| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
2085
|
Mon Nov 20 22:20:22 2006 |
 | Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.6.2-1734 | Re: Re: $long_name in Moptions |
| Fergus Lynch wrote: | Hi,
Is there a way of having $long_name in 'Moptions'?
We use ELOG (amongst other things!) to allocate work out to Developers (who are all configured as ELOG users) I would like to use 'checkbox' functionality to allocate out a task to more than one developer. Currently only a single developer is chosen from a drop down list. |
This was not possible until now, so I implemented the option
Type <attribute> = muserlist
which gives you checkboxes (= multi-userlist) for all users instead of a drop down list. This feature is implemented starting from revision 1758 and it will be contained in the next release of elog. |
|
2086
|
Tue Nov 21 09:44:30 2006 |
| Fergus Lynch | flynch@alternativenetworks.com | Question | Windows | 2.6.2-1734 | Re: Re: $long_name in Moptions |
| Stefan Ritt wrote: |
| Fergus Lynch wrote: | Hi,
Is there a way of having $long_name in 'Moptions'?
We use ELOG (amongst other things!) to allocate work out to Developers (who are all configured as ELOG users) I would like to use 'checkbox' functionality to allocate out a task to more than one developer. Currently only a single developer is chosen from a drop down list. |
This was not possible until now, so I implemented the option
Type <attribute> = muserlist
which gives you checkboxes (= multi-userlist) for all users instead of a drop down list. This feature is implemented starting from revision 1758 and it will be contained in the next release of elog. |
WowThat was quick, I'll implement this morning. Many thanks for introducing this, ELOG is such a good tool.
Many Thanks
Fergus |
|
2087
|
Tue Nov 21 11:14:48 2006 |
| Fergus Lynch | flynch@alternativenetworks.com | Question | Windows | 2.6.2-1734 | Re: Re: $long_name in Moptions |
| Stefan Ritt wrote: |
| Fergus Lynch wrote: | Hi,
Is there a way of having $long_name in 'Moptions'?
We use ELOG (amongst other things!) to allocate work out to Developers (who are all configured as ELOG users) I would like to use 'checkbox' functionality to allocate out a task to more than one developer. Currently only a single developer is chosen from a drop down list. |
This was not possible until now, so I implemented the option
Type <attribute> = muserlist
which gives you checkboxes (= multi-userlist) for all users instead of a drop down list. This feature is implemented starting from revision 1758 and it will be contained in the next release of elog. |
Hi Stefan, apologies if I am being a bit dense (!) When I download the latest windows binary it extracts to ELOG V2.6.2-1749. Where could I get revision 1758 >
Thanks in advance
Fergus |
|
66069
|
Fri Nov 21 18:21:36 2008 |
 | Dennis Seitz | dseitz@berkeley.edu | Question | All | latest | Re: Re: $entry time not readable by Subst, else not datetime type? - possible Preset bug? |
| Dennis Seitz wrote: |
| Stefan Ritt wrote: |
| Dennis Seitz wrote: | | Do you mean '$entry time', or did you create a new parameter? (I don't see $entry date in the elogd.cfg reference) |
Yes, of course I mean '$entry time', sorry for the misspelling. |
Well, we really appreciate the way you keep adding features and making improvements. I thought you might have slipped a new one in! |
FYI, I think there's a little bug in the datetime vs $date implementation.
Here's a section of my config file implementing a "Last Edit" field:
Type Last Edit = datetime
Preset Last Edit =$date
Locked Attributes = Last Edit
Subst on edit Last Edit = $date
Start page = ?rsort=Last Edit
I expected that "Preset Last Edit =$date" would set Last Edit to the current date when I create a new entry. In fact that leaves the field empty, or at least not in datetime format.
I found that using this instead works:
Preset Last Edit =$entry time
which seems contradictory since
Subst on edit Last Edit = $date
works fine. |
|
66079
|
Mon Nov 24 20:00:05 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | latest | Re: Re: $entry time not readable by Subst, else not datetime type? - possible Preset bug? |
| Dennis Seitz wrote: | FYI, I think there's a little bug in the datetime vs $date implementation.
Here's a section of my config file implementing a "Last Edit" field:
Type Last Edit = datetime
Preset Last Edit =$date
Locked Attributes = Last Edit
Subst on edit Last Edit = $date
Start page = ?rsort=Last Edit
I expected that "Preset Last Edit =$date" would set Last Edit to the current date when I create a new entry. In fact that leaves the field empty, or at least not in datetime format.
I found that using this instead works:
Preset Last Edit =$entry time
which seems contradictory since
Subst on edit Last Edit = $date
works fine. |
Do you have an old version of elog? Using the current version with a configuration file:
Attributes = Author, Type, Last Edit
Type Last Edit = datetime
Preset Last Edit =$date
Locked Attributes = Last Edit
Start page = ?rsort=Last Edit
I get the correct behavior:
 |
|
66080
|
Tue Nov 25 17:01:55 2008 |
| Dennis Seitz | dseitz@berkeley.edu | Question | All | 2.7.3 | Re: Re: $entry time not readable by Subst, else not datetime type? - possible Preset bug? |
| Stefan Ritt wrote: |
| Dennis Seitz wrote: | FYI, I think there's a little bug in the datetime vs $date implementation.
Here's a section of my config file implementing a "Last Edit" field:
Type Last Edit = datetime
Preset Last Edit =$date
Locked Attributes = Last Edit
Subst on edit Last Edit = $date
Start page = ?rsort=Last Edit
I expected that "Preset Last Edit =$date" would set Last Edit to the current date when I create a new entry. In fact that leaves the field empty, or at least not in datetime format.
I found that using this instead works:
Preset Last Edit =$entry time
which seems contradictory since
Subst on edit Last Edit = $date
works fine. |
Do you have an old version of elog? Using the current version with a configuration file:
Attributes = Author, Type, Last Edit
Type Last Edit = datetime
Preset Last Edit =$date
Locked Attributes = Last Edit
Start page = ?rsort=Last Edit
I get the correct behavior:
|
Yes, I'm using 2.7.3 - I'll try upgrading, sorry. I'll reply with the outcome. |
|
66102
|
Tue Dec 9 00:22:41 2008 |
| Dennis Seitz | dseitz@berkeley.edu | Question | All | 2.7.5 | Re: Re: $entry time not readable by Subst, else not datetime type? - possible Preset bug? |
| Dennis Seitz wrote: |
| Stefan Ritt wrote: |
| Dennis Seitz wrote: | FYI, I think there's a little bug in the datetime vs $date implementation.
Here's a section of my config file implementing a "Last Edit" field:
Type Last Edit = datetime
Preset Last Edit =$date
Locked Attributes = Last Edit
Subst on edit Last Edit = $date
Start page = ?rsort=Last Edit
I expected that "Preset Last Edit =$date" would set Last Edit to the current date when I create a new entry. In fact that leaves the field empty, or at least not in datetime format.
I found that using this instead works:
Preset Last Edit =$entry time
which seems contradictory since
Subst on edit Last Edit = $date
works fine. |
Do you have an old version of elog? Using the current version with a configuration file:
Attributes = Author, Type, Last Edit
Type Last Edit = datetime
Preset Last Edit =$date
Locked Attributes = Last Edit
Start page = ?rsort=Last Edit
I get the correct behavior:
|
Yes, I'm using 2.7.3 - I'll try upgrading, sorry. I'll reply with the outcome. |
Everything works fine with 2.7.5, thanks! |
|
65881
|
Thu May 15 01:06:21 2008 |
| Dennis Seitz | dseitz@cosmology.berkeley.edu | Question | All | latest | Re: Re: $entry time not readable by Subst, else not datetime type? |
| Dennis Seitz wrote: | I posted this on the end of an earlier thread but I thought it might be better to repost as a separate thread:
Thank you for pointing out the method to identify an attribute as a datetime type so that it will sort properly. I now have created my "Last Edit" attribute in several
preexisting logbooks.
I want to use
Start page = ?rsort=Last Edit
to set the default sorting of each logbook to be by Last Edit.
However, all of the entries made before I added Last Edit have no value for that field, so they are all grouped together at the end of the sort. So I
decided to go through the older entries and set Last Edit equal to the original entry date, as a starting value.
I tried to use the command
Subst on edit Last Edit = $entry time
but it gives a "-" for the Last Edit value when I edit an entry.
I think this is because $entry time is not a variable supported by Subst. Can you add that support, or else tell me if you know a better way to go about
doing what I'm attempting? Is there perhaps a way to globally process a group of entries in a logbook and set one attribute's value to be equal to
another's? To reiterate, I want to initialize Last Edit = $entrytime for all entries that have not been re-edited.
Thanks |
OK, now I realize how stupid I sound here. To partially answer my own question: $entry time is a string and Last Edit is now a number since I have changed it to the datetime type so that it will sort properly.
So I can't make Last Edit = $entry time. Is there some way I can access the entry time in datetime format so that I can set Last Edit equal to that?
Sorry if I'm missing something obvious, I'm confused... |