| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
2125
|
Tue Feb 6 21:46:59 2007 |
 | Grant Jeffcote | grant@jeffcote.org | Request | Windows | | Re: Tool Tips |
| Stefan Ritt wrote: |
| Grant Jeffcote wrote: | | I can't seem to get the Tooltips to show up using the 'ROptions' (radio buttons) though? Could you check if it is available for this please? |
Did I tell that it also works with 'ROptions' ??? It does not! I implemented this just now in revision 1788. The fix will be contained in the next release. |
Sorry, just checking. 
Many thanks Stefan  |
|
2162
|
Tue Mar 13 17:27:49 2007 |
 | Justin Ellison | justin@techadvise.com | Request | | Current | Addition of a "Restrict edit attribute" option? |
It would be a nice addition to have a config file option named "Restrict edit attribute".
Basically, I would like to have an attribute that was either:
a) An Option Attribute named Status with options of "Open" or "Closed"
b) An Option Attribute named Closed that was boolean.
Then, we could leave the item as editable until either choice "a" above was set to closed or choice "b" was true, at which point only admins could edit the item.
Sound plausible?
Justin |
|
2163
|
Tue Mar 13 20:58:07 2007 |
 | Stefan Ritt | stefan.ritt@psi.ch | Request | | Current | Re: Addition of a "Restrict edit attribute" option? |
| Justin Ellison wrote: | It would be a nice addition to have a config file option named "Restrict edit attribute".
Basically, I would like to have an attribute that was either:
a) An Option Attribute named Status with options of "Open" or "Closed"
b) An Option Attribute named Closed that was boolean.
Then, we could leave the item as editable until either choice "a" above was set to closed or choice "b" was true, at which point only admins could edit the item.
|
Conditional attributes? Like:
Attributes = ..., Status
Options Status = Open{1}, Closed{2}
{2}Locked attributes = Status
Unfortunately once it's locked, the admin has to change the config file to unlock it. |
|
2167
|
Wed Mar 14 15:03:41 2007 |
| Justin Ellison | justin@techadvise.com | Request | | Current | Re: Addition of a "Restrict edit attribute" option? |
Sorry, I didn't explain it enough.
This feature is like "Restrict edit time", but instead of setting an entire entry as read only after n hours, we set it read only if attribute y is true. Admin would be able to go in and reset that attribute to false to unlock the entry for editing, but no one else would be able to.
That make more sense?
Justin |
|
2168
|
Wed Mar 14 15:06:27 2007 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | | Current | Re: Addition of a "Restrict edit attribute" option? |
| Justin Ellison wrote: | Sorry, I didn't explain it enough.
This feature is like "Restrict edit time", but instead of setting an entire entry as read only after n hours, we set it read only if attribute y is true. Admin would be able to go in and reset that attribute to false to unlock the entry for editing, but no one else would be able to. |
I understand what you want. The conditional attributes I showed you give you that functionality, except that unlocking is a bit painful for the admin (has to edit the config file each time). Sorry, but that's all I can give you. |
|
2169
|
Wed Mar 14 15:43:51 2007 |
| Justin Ellison | justin@techadvise.com | Request | | Current | Re: Addition of a "Restrict edit attribute" option? |
| Stefan Ritt wrote: |
I understand what you want. The conditional attributes I showed you give you that functionality, except that unlocking is a bit painful for the admin (has to edit the config file each time). Sorry, but that's all I can give you. |
Now I understand what you were getting at. Sorry for the confusion. That should work fine for us - unlocking is something that shouldn't ever happen.
Thanks for the quick response!
Justin |
|
2175
|
Mon Mar 26 11:45:07 2007 |
 | Fergus Lynch | flynch@alternativenetworks.com | Request | Windows | ELOG V2.6. | Global "MOptions" |
Hi,
We have ELOG configured for virtually every conceivable use in our IT Operation dept and it is fantastically useful and easy to use. One result of this - naturally! - is that we have quiet a few logbooks.
Many of these logbooks share the same attributes - especially Moptions for equipment lists - which is fine but requires manually copying and pasting Moption lists into multiple logbooks to keep everything synchronized.
Would it be an option to have Global "MOptions" - perhaps configured in the 'global options' file - which can be called up and referenced in all logbooks?
Just an idea -
Cheers
Fergus |
|
2176
|
Mon Mar 26 13:03:05 2007 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Windows | ELOG V2.6. | Re: Global "MOptions" |
| Fergus Lynch wrote: | | Would it be an option to have Global "MOptions" - perhaps configured in the 'global options' file - which can be called up and referenced in all logbooks? |
Sure, that's possible alreay with the current version. Just put your MOptions statement under [global] and it will be used in all logbooks. If a specific logbook uses different MOptions, put the a second MOptions list under that logbook's section and it will overwrite the global setting. |