| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
69272
|
Wed Dec 2 22:45:16 2020 |
 | Harry Martin | harrymartin772@gmail.com | Question | Linux | Windows | Mac OSX | All | Other | 3.1.3 | length of condition names |
The documentation describing the use of conditionals uses a single character (letter or number) for names of conditions. I don't see any update/change to that rule anywhere in the docs.
I have been using multi-character condition names successfully. I find these are easier to use since they can be more descriptive of each condition. It works, but I am concerned I may be doing something that might not be supported going forward. (It is simple enough to change these, but I'd prefer to know if this practice is acceptable.)
Thank you, again, for this fine (and, may I add, fun?) tool. I'm having a good time with it! |
|
69273
|
Thu Dec 3 01:51:49 2020 |
 | Harry Martin | harrymartin772@gmail.com | Question | Linux | Windows | 3.1.3 | Re: Options <...> vs ROptions <...> |
Same problem here, in version 3.1.3. It would be very nice if this worked.
| Wolfgang Bayer wrote: |
|
According to section "Syntax of elogd.cfg" of the "Administrator's Guide" Options <attribute> = <list> and ROptions <attribute> = <list> should be the same. But there is a litle difference, because choosing an entry of the Options-pull-down menu causes a reload of the entry mask while choosing a ROption-radio-button the entry mask is not reloaded. This causes a problem using conditional attributes. The condition is only paid attention to in case of Options but not in case of ROptions. In my case I would like to use ROption, as it is faster to set a radio button than to choose an item in a pull-down menu, but I can't as I have also to use conditional attributes. Is there any solution?
|
|
|
69274
|
Thu Dec 3 01:53:59 2020 |
| Harry Martin | harrymartin772@gmail.com | Bug report | Windows | 2.7.7-2246 | Re: Change / List Change doen't work anymore? |
| Stefan Ritt wrote: | Yepp, the documentation was wrong. I fixed it.
Stefan |
Thank you. |
|
69275
|
Thu Dec 3 09:57:20 2020 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | Windows | Mac OSX | All | Other | 3.1.3 | Re: length of condition names |
You can easily use multi-character conditionals, up to 256 chars.
| Harry Martin wrote: |
|
The documentation describing the use of conditionals uses a single character (letter or number) for names of conditions. I don't see any update/change to that rule anywhere in the docs.
I have been using multi-character condition names successfully. I find these are easier to use since they can be more descriptive of each condition. It works, but I am concerned I may be doing something that might not be supported going forward. (It is simple enough to change these, but I'd prefer to know if this practice is acceptable.)
Thank you, again, for this fine (and, may I add, fun?) tool. I'm having a good time with it!
|
|
|
69276
|
Thu Dec 3 09:58:44 2020 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | Windows | 3.1.3 | Re: Options <...> vs ROptions <...> |
For conditional attributes, you have to use Options, not ROptions. Maybe I will implement that one day, but only if I will have plenty of time...
| Harry Martin wrote: |
|
Same problem here, in version 3.1.3. It would be very nice if this worked.
| Wolfgang Bayer wrote: |
|
According to section "Syntax of elogd.cfg" of the "Administrator's Guide" Options <attribute> = <list> and ROptions <attribute> = <list> should be the same. But there is a litle difference, because choosing an entry of the Options-pull-down menu causes a reload of the entry mask while choosing a ROption-radio-button the entry mask is not reloaded. This causes a problem using conditional attributes. The condition is only paid attention to in case of Options but not in case of ROptions. In my case I would like to use ROption, as it is faster to set a radio button than to choose an item in a pull-down menu, but I can't as I have also to use conditional attributes. Is there any solution?
|
|
|
|
69278
|
Thu Dec 3 19:11:38 2020 |
| Illam Pakkirisamy | illam@senseeker.com | Info | Windows | ELOG V3.1.4-a04 | How to increase TEXT_SIZE to address entry text limit |
Hi,
I'm trying to increase the entry text constraint but not sure how to do this. Couldn't find it in the documentation or may be I missed it. Appreciate your help.
Thanks.
Illam
|
|
69279
|
Fri Dec 4 02:03:56 2020 |
| Harry Martin | harrymartin772@gmail.com | Question | Linux | Windows | Mac OSX | All | Other | 3.1.3 | Re: length of condition names |
Could we update the doc for this?
| Stefan Ritt wrote: |
|
You can easily use multi-character conditionals, up to 256 chars.
| Harry Martin wrote: |
|
The documentation describing the use of conditionals uses a single character (letter or number) for names of conditions. I don't see any update/change to that rule anywhere in the docs.
I have been using multi-character condition names successfully. I find these are easier to use since they can be more descriptive of each condition. It works, but I am concerned I may be doing something that might not be supported going forward. (It is simple enough to change these, but I'd prefer to know if this practice is acceptable.)
Thank you, again, for this fine (and, may I add, fun?) tool. I'm having a good time with it!
|
|
|
|
69280
|
Tue Dec 15 14:50:55 2020 |
| Satyajit Jena | satya.ino@gmail.com | Question | Linux | 3.1.4 | Is there a way to upload a file in custom input? |
Hi,
I am trying to implement a Custom input forms by following this https://elog.psi.ch/elogs/Contributions/49. Is there a way to also insert an image or files to it? I want to take a snap from the iPad and want that to go as an attachment or attach a file(s) into the form. Is there a way to do that?
Your suggestions are highly appreciated.
Regards,
sjena
|