| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
66871
|
Thu Jul 29 13:45:47 2010 |
 | soren poulsen | soren.poulsen@cern.ch | Question | Linux | 2.7.8 | Re: Subst variables and Execute |
| Stefan Ritt wrote: |
|
| soren poulsen wrote: |
|
There is sometimes a problem with substitutions like "Execute delete = echo $message id".
It seems the problem is that if you delete a logbook entry that is not created with the current logbook attributes, the substitution variables are replaced with the variable name, and not the variable value.
In this example, according to the log file it becomes SHELL "message id" instead of SHELL "234", if the logbook entry is 234.
Soren
|
I tried to reproduce it, but it always worked for me. So I need a step-by-step instruction from you on how to reproduce the problem, ideally starting from the demo logbook from the distribution. Only if I can reproduce the problem, I will be able to fix it.
|
It is of course my job to reproduce it (and explain how-to). Thanks for your consideration. |
|
66870
|
Wed Jul 28 22:03:26 2010 |
| Dennis Seitz | dseitz@berkeley.edu | Request | All | 2.7.7 | Re: alphabetize Quick Filter items? |
| Stefan Ritt wrote: |
|
| Dennis Seitz wrote: |
|
| Stefan Ritt wrote: |
|
| Dennis Seitz wrote: |
|
| |
|
Ok, I implemented
Sort attribute options = 1
in the current SVN revision.
|
I've tried adding this statement to my cfg file but the attributes are still unsorted in the QuickFilter menus. Was this implemented in 2.7.7?
Shouldn't an existing configuration file entry like
Options Type = C, D, A, B
be sorted in the QuickFilter menu as A B C D?
|
You need revision 2252 or later. So you have to upgrade to 2.7.8.
|
We have upgraded to 2.7.8 but this still doesn't seem to work. The quick menus are still unsorted. Does it work for you?
|
Sorry, there was a typo, you need
Sort attribute options <attribute> = 1
where <attribute> is the name of the attribute to be sorted (in case you want some attributes sorted, but not all).
|
That did the trick. That was a good idea, to give us the option of which attributes to sort, too. Thanks again for adding this feature! |
|
66869
|
Wed Jul 28 17:32:15 2010 |
| Bryan Moffit | moffit@jlab.org | Question | Linux | 2.7.8-2278 | Re: Disable forward/backward navigation keystrokes? |
| Stefan Ritt wrote: |
|
| Bryan Moffit wrote: |
|
I wondered if there was a config line that enabled/disabled the forward and backward navigation keystrokes that were implemented in 2.7.0?
The current definitions (Control-PgUp/PgDown/Home/End) interfere with those keys I use to navigate between tabs in Firefox. It'd be nice if they could either be turned off.. or redefined.
|
They are defined in
<ELOG directory>\scripts\elcode.js
Just go to the browse(evt) function and redefine or remove them there.
|
Got it to work as desired.
Thanks for your help and your quick response. |
|
66868
|
Wed Jul 28 17:26:17 2010 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.7.8-2278 | Re: Disable forward/backward navigation keystrokes? |
| Bryan Moffit wrote: |
|
I wondered if there was a config line that enabled/disabled the forward and backward navigation keystrokes that were implemented in 2.7.0?
The current definitions (Control-PgUp/PgDown/Home/End) interfere with those keys I use to navigate between tabs in Firefox. It'd be nice if they could either be turned off.. or redefined.
|
They are defined in
<ELOG directory>\scripts\elcode.js
Just go to the browse(evt) function and redefine or remove them there. |
|
66867
|
Wed Jul 28 17:21:31 2010 |
 | Bryan Moffit | moffit@jlab.org | Question | Linux | 2.7.8-2278 | Disable forward/backward navigation keystrokes? |
I wondered if there was a config line that enabled/disabled the forward and backward navigation keystrokes that were implemented in 2.7.0?
The current definitions (Control-PgUp/PgDown/Home/End) interfere with those keys I use to navigate between tabs in Firefox. It'd be nice if they could either be turned off.. or redefined. |
|
66866
|
Wed Jul 28 17:15:33 2010 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | All | 2.7.7 | Re: alphabetize Quick Filter items? |
| Dennis Seitz wrote: |
|
| Stefan Ritt wrote: |
|
| Dennis Seitz wrote: |
|
| |
|
Ok, I implemented
Sort attribute options = 1
in the current SVN revision.
|
I've tried adding this statement to my cfg file but the attributes are still unsorted in the QuickFilter menus. Was this implemented in 2.7.7?
Shouldn't an existing configuration file entry like
Options Type = C, D, A, B
be sorted in the QuickFilter menu as A B C D?
|
You need revision 2252 or later. So you have to upgrade to 2.7.8.
|
We have upgraded to 2.7.8 but this still doesn't seem to work. The quick menus are still unsorted. Does it work for you?
|
Sorry, there was a typo, you need
Sort attribute options <attribute> = 1
where <attribute> is the name of the attribute to be sorted (in case you want some attributes sorted, but not all). |
|
66865
|
Wed Jul 28 17:08:55 2010 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.7.8 | Re: Subst variables and Execute |
| soren poulsen wrote: |
|
There is sometimes a problem with substitutions like "Execute delete = echo $message id".
It seems the problem is that if you delete a logbook entry that is not created with the current logbook attributes, the substitution variables are replaced with the variable name, and not the variable value.
In this example, according to the log file it becomes SHELL "message id" instead of SHELL "234", if the logbook entry is 234.
Soren
|
I tried to reproduce it, but it always worked for me. So I need a step-by-step instruction from you on how to reproduce the problem, ideally starting from the demo logbook from the distribution. Only if I can reproduce the problem, I will be able to fix it. |
|
66864
|
Wed Jul 28 17:01:06 2010 |
| Dennis Seitz | dseitz@berkeley.edu | Request | All | 2.7.7 | Re: alphabetize Quick Filter items? |
| Stefan Ritt wrote: |
|
| Dennis Seitz wrote: |
|
| Stefan Ritt wrote: |
|
| Dennis Seitz wrote: |
|
| Stefan Ritt wrote: |
|
| Dennis Seitz wrote: |
|
Hi Stefan,
I'd like to request a feature: automatic alphabetization of the items in the Quick Filter menus.
We track quite a few detector assemblies, which are produced with non-sequential designations. It would be useful if the Quick Filter list was automatically sorted alphabetically to make it more convenient for folks to find a particular item.
I know people can always search by designation but it would be handy to have this alpha sorting feature. Would it be possible to include that in a future release?
Thanks again for a *very* useful logging system!
Dennis
|
The order of items in a Quick Filter menu is exactly as in the configuration file. Like if you have items
Options Type = C, D, A, B
they are shown like that in the quick filter menu. If you want to sort them, just do the sorting yourself in the configuration file like
Options Type = A, B, C, D
I have not implemented automatic sorting since some people want a different order, like some main topics at top. So by following the order from the configuration file, everybody can be satisfied just by chaning the order in the config file.
- Stefan
|
Yes, I have been manually sorting and resorting. We have extendable attributes and the list keeps growing so I have to resort every so often. I thought perhaps a simple alphanumeric sort as an option would be popular with most users so I thought I'd ask for it. It would really simplify things for me. Users who want to sort manually could do so by disabling the option. It never hurts to ask!
|
Ok, I implemented
Sort attribute options = 1
in the current SVN revision.
|
I've tried adding this statement to my cfg file but the attributes are still unsorted in the QuickFilter menus. Was this implemented in 2.7.7?
Shouldn't an existing configuration file entry like
Options Type = C, D, A, B
be sorted in the QuickFilter menu as A B C D?
|
You need revision 2252 or later. So you have to upgrade to 2.7.8.
|
We have upgraded to 2.7.8 but this still doesn't seem to work. The quick menus are still unsorted. Does it work for you? |