It depends on how you actually call the elog client, but it outputs a message

 Message successfully transmitted, ID=(new message id)

to the console upon successful transmission. Maybe you can catch this and evaluate?

Hi!

Looking at your config file it seems that a lot of the attributes are not user-specified but rather auto-generated content. You may want to consider using the elog client to submit such entries; this might avoid performance issues related to communication of the server with the web browser used for entry generation. This way, event entries can even be automatically created by other software rather than having a user to submit them.

Yoshio

• define an additional logbook attribute, say "UTC Date"
  
• preset it on entry creation and submission with the UTC timestamp (cf. section "Attributes" of the ELog configuration guide):

  Preset UTC Date = $utcdate
  Subst UTC Date = $utcdate

• prevent the attribute from being changed manually by adding it to the

  Locked Attributes = < ... >

  and

  Fixed Attributes Edit = < ... >

  lists, respectively.
  You may also have to add it to the

  Remove on reply = < ... >

  list if replies turn out to keep the "UTC Date" value of the original entry.
  

How do I make this section Wider or Shorter in the 2.7.8 version?
Maybe I did something to make it shorter? ELCode shows as a full box but plain txt is very short box. 

Looks like it works :)

Code need to be put in tags:

<pre><code class="sql">...</code></pre>

but it works.

Thank you :D

Best Regards

Daniel Sajdyk

#include <stdio.h>
int main()
{
   // printf() displays the string inside quotation
   printf("C Programming");
   return 0;
}