Format in "Thread display", posted by Eoin Butler on Sat Jun 18 20:29:25 2011
|
Is is possible to add formatting (such as <b> tags, etc..) to the "thread display" option? |
Hide blank fields when displaying logbook entry, posted by Rudy Taraschi on Thu Jun 23 15:57:34 2016
|
Hi, I have a logbook with attributes Tool1, Tool2, and Tool3. When viewing a completed entry, what I want to do is see Tool2 or Tool3 only if they are non-zero, and don't want to see them if blank. Basically, a "Hide if blank" option. I couldn't find it - if it doesn't exist, are there any tricks to simulate it? |
More than 100 attributes , posted by JD on Wed Jun 29 16:07:32 2016
|
I am modifying the elogd.cfg automatically with a script. The Script fetches a list of systems from a LDAP database and writes them into an "Options" line in the elog.cfg.
Everything worked fine, until we hit the critical number of 100 attributes. I saw this is also stated in the manual.
Is there any workaround? I downloaded the source code and hat a quit look, but couldn't find the section which is responsible for this behavior.
Is there a reason for this limit?
Thanks
Jonathan |
Re: More than 100 attributes , posted by Stefan Ritt on Wed Jun 29 16:58:15 2016
|
The limit is in the variable
#define MAX_N_ATTR 100
in elogd.c. If you increase it and recompile, it could work, but at some time you will get a stack overflow since arrays with that size are dynamically allocated on the stack, and depending on your compiler settings the stack size is only finite.
Stefan
JD wrote: |
I am modifying the elogd.cfg automatically with a script. The Script fetches a list of systems from a LDAP database and writes them into an "Options" line in the elog.cfg.
Everything worked fine, until we hit the critical number of 100 attributes. I saw this is also stated in the manual.
Is there any workaround? I downloaded the source code and hat a quit look, but couldn't find the section which is responsible for this behavior.
Is there a reason for this limit?
Thanks
Jonathan
|
|
Re: More than 100 attributes , posted by JD on Thu Jun 30 14:00:43 2016
|
Thank you Stefan, I think then I will leave it at the default value. I need a stable Systen
Stefan Ritt wrote: |
The limit is in the variable
#define MAX_N_ATTR 100
in elogd.c. If you increase it and recompile, it could work, but at some time you will get a stack overflow since arrays with that size are dynamically allocated on the stack, and depending on your compiler settings the stack size is only finite.
Stefan
JD wrote: |
I am modifying the elogd.cfg automatically with a script. The Script fetches a list of systems from a LDAP database and writes them into an "Options" line in the elog.cfg.
Everything worked fine, until we hit the critical number of 100 attributes. I saw this is also stated in the manual.
Is there any workaround? I downloaded the source code and hat a quit look, but couldn't find the section which is responsible for this behavior.
Is there a reason for this limit?
Thanks
Jonathan
|
|
|
Multiple outcomes to a conditional attribute, posted by Sofian Jafar on Tue Jul 12 08:06:36 2016
|
Hi,
First of all, thanks for all the great work, we all thank you here at SESAME synchrotron 
I am trying to set a conditional attribute where selecting one option in that attribute should trigger multiple outcomes as shown below:
Options Type = Fault{1_1&1_2}, Test{2_1&2_2}, Report{2_1&2_2}
{1_1} Options Fault Status = Open{a}, Fixed{b}
{2_1} Preset Fault Status = NA
{1_2} Preset Icon = attn.png
{2_2} Preset Icon = icon1.gif
I tries adding "&" as shown but that didn't work, my goal is to have 1_1 and 1_2 triggered whenever I select "Fault" as type, how can I do that?
Thanks in advance.
Cheers,
Sofian.
|
Re: Multiple outcomes to a conditional attribute, posted by Andreas Luedeke on Tue Jul 12 08:31:37 2016
|
Hi Sofian,
it should work like this:
Options Type = Fault{1}, Test{2}, Report{3}
{1} Options Fault Status = Open{a}, Fixed{b}
{2,3} Preset Fault Status = NA
{1} Preset Icon = attn.png
{2,3} Preset Icon = icon1.gif
It is described under "Multiple conditions" in the documentation (https://midas.psi.ch/elog/config.html#conditional).
Cheers and good luck!
Andreas
Sofian Jafar wrote: |
Hi,
First of all, thanks for all the great work, we all thank you here at SESAME synchrotron 
I am trying to set a conditional attribute where selecting one option in that attribute should trigger multiple outcomes as shown below:
Options Type = Fault{1_1&1_2}, Test{2_1&2_2}, Report{2_1&2_2}
{1_1} Options Fault Status = Open{a}, Fixed{b}
{2_1} Preset Fault Status = NA
{1_2} Preset Icon = attn.png
{2_2} Preset Icon = icon1.gif
I tries adding "&" as shown but that didn't work, my goal is to have 1_1 and 1_2 triggered whenever I select "Fault" as type, how can I do that?
Thanks in advance.
Cheers,
Sofian.
|
|
Re: Multiple outcomes to a conditional attribute, posted by Stefan Ritt on Tue Jul 12 08:37:42 2016
|
What about this:
Options Type = Fault{1}, Test{2}, Report{3}
{1} Options Fault Status = Open{a}, Fixed{b}
{2,3} Preset Fault Status = NA
{1} Preset Icon = attn.png
{2,3} Preset Icon = icon1.gif
-Stefan
Sofian Jafar wrote: |
Hi,
First of all, thanks for all the great work, we all thank you here at SESAME synchrotron 
I am trying to set a conditional attribute where selecting one option in that attribute should trigger multiple outcomes as shown below:
Options Type = Fault{1_1&1_2}, Test{2_1&2_2}, Report{2_1&2_2}
{1_1} Options Fault Status = Open{a}, Fixed{b}
{2_1} Preset Fault Status = NA
{1_2} Preset Icon = attn.png
{2_2} Preset Icon = icon1.gif
I tries adding "&" as shown but that didn't work, my goal is to have 1_1 and 1_2 triggered whenever I select "Fault" as type, how can I do that?
Thanks in advance.
Cheers,
Sofian.
|
|
|