| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
66515
|
Tue Aug 11 17:46:33 2009 |
 | Dennis Seitz | dseitz@berkeley.edu | Comment | Linux | 2.7.7-2251 | Re: Comment on: Alphabetize Quick Option filter | Yes, many thanks, Stefan, from me, too! It's really great that you respond so quickly to requests and suggestions.
And thanks to David for the fine tuning, great suggestion.
Dennis
> Thanks Stefan! Works great.
>
> > Ok, that makes sense, so I changed it to
> >
> > Sort Attribute Options Status = 1
> >
> > as you suggested.
> >
> > > (For some reason I could not add this in Dennis's thread.)
> > >
> > > I like this new feature, BUT
> > >
> > > I happen to have two Options: Options System, and Options Status.
> > >
> > > System are a very few items, whereas Status has a long list, which, like Dennis's example, can be added to.
> > > Keeping the latter in alpha order is great, but it's a shame that the cost is that Options System are also
> > > sorted alphabetically, whereas it has a natural order which it would be preferable to keep - for example (and
> > > this is made up)
> > >
> > > Options System: 3.1, NT, 2000, XP, Vista
> > >
> > > where the natural order here is chronological.
> > >
> > > Perhaps the configuration file option could be more specific, for example
> > >
> > > Sort attribute Options Status = 1
> > >
> > > which would then NOT sort Options System. If both are needed to be sorted, both should be specified, or back to
> > > the original syntax which defaults to sort *all* Options. |
|
66835
|
Thu Jun 3 06:14:50 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: |
|
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? |
|
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? |
|
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! |
|
66880
|
Thu Aug 19 22:58:45 2010 |
 | Dennis Seitz | dseitz@berkeley.edu | Bug report | All | 2.7.8 | Elog v2.7.8 does not show substituted attributes while editing or replying | Since we updated to 2.7.8 we've found a problem.
Previously, when we used
Subst on reply subject = Re: $subject
The new "Re: " text would appear in the "subject" field while the user was editing their reply, and they could edit or delete it.
Since 2.7.8, however, it does not appear while editing, but shows up only after the user submits their entry. We would prefer that this appears while the user is editing, because in some cases we want the users to have the option to modify this text. Was this intentional? Is there a way to restore the previous functionality?
Thank you! |
|
Draft
|
Wed Mar 24 16:11:04 2021 |
| Dominic Schneider | dschneider@mein.gmx | Question | Linux | 3.1.3-1-1 | Pre-fill | Hi all together,
I struggle a lot with the following problem:
I try to prefill certain attributes with the value of exactly the same attribute in the last entry made in the same logbook.
I know I have to go with Preset, tried a view hours and searched the forum but i didn't find a thing. Am I overlooking a flag, an option or whatever, or is there just not such a functionality (which I dont believe)?
I thought about:
Preset Test_Attribute = $Test_attribute
Preset Test_Attribute = Re:$Test_attribute
Preset Test_Attribute = $shell(Command to somehow get last entry and this attributes value)
Not succesful though.
I would be very thankful for help, thanks in advance. |
|
69326
|
Wed Mar 24 16:20:37 2021 |
| Dominic Schneider | dschneider@mein.gmx | Question | Linux | 3.1.3-1-1 | Pre-fill Attribute with last entry | Hi all together,
I struggle a lot with the following problem:
I try to prefill certain attributes with the value of exactly the same attribute in the last entry made in the same logbook.
I know I have to go with Preset, tried a view hours and searched the forum but i didn't find a thing. Am I overlooking a flag, an option or whatever, or is there just not such a functionality (which I dont believe)?
I thought about:
Preset Test_Attribute = $Test_attribute
Preset Test_Attribute = Re:$Test_attribute
Preset Test_Attribute = $shell(Command to somehow get last entry and this attributes value)
Not succesful though.
I would be very thankful for help, thanks in advance. |
|
69330
|
Wed Mar 24 19:30:50 2021 |
| Dominic Schneider | dschneider@mein.gmx | Question | Linux | 3.1.3-1-1 | Re: Pre-fill Attribute with last entry | Hi Stefan, hi Sebastian,
thank you for your help. Ok I see its not that simple.
Is there maybe a way of executing a Script on submitting, writing the values of the Attributes into an temporary file and loading the values from this file via a preset shell script when opening a NEW entry?
Best wishes & thanks in advance
| Sebastian Schenk wrote: |
|
Sorry Stefan, but it is possible as you have the scripting ability.
The idea is to use "Preset Test_Attribute = $shell(script_to_get_the_last_entry)", where the script asks elog about the details and parses them.
The problem here is, that the elogd already is working to resolve the click on "new entry" request (or similar) and the script can't call elogd until the page is delievered, what is to late.
(If it would, the elogd will hang.)
So the script either has to directly parse all the entry.log files in the logbook folder or you need a second elogd running, which can answer the request from the script.
This second elogd could run on a different port and it doen't need to be public as it only answers internal requests and could use the same config as the "primary" elogd.
My idea for the script uses the python elog module to establish the connection and do the parsing.
I hope this helps as a workaround.
Best wishes,
Sebastian
| Stefan Ritt wrote: |
|
Nope, there is no way to acces the last value of an attribute. Sorry.
Stefan
| Dominic Schneider wrote: |
|
Hi all together,
I struggle a lot with the following problem:
I try to prefill certain attributes with the value of exactly the same attribute in the last entry made in the same logbook.
I know I have to go with Preset, tried a view hours and searched the forum but i didn't find a thing. Am I overlooking a flag, an option or whatever, or is there just not such a functionality (which I dont believe)?
I thought about:
Preset Test_Attribute = $Test_attribute
Preset Test_Attribute = Re:$Test_attribute
Preset Test_Attribute = $shell(Command to somehow get last entry and this attributes value)
Not succesful though.
I would be very thankful for help, thanks in advance.
|
|
|
|
|