I have two logbooks running, one for current accounts and one for non-active ones. The idea is to move an entry from one logbook to the other once an account becomes non-active. Both logbooks share some attributes (e.g. the name of the account, its creation date, ...), but both also have some uniqe attributes.

While I was playing with this set-up, I ran into a problem:

1. Move an existing entry from current to non-active.
   • "Type" and "Status" have options. "Created" and "Archived" are in date format.
   • "Created" and "Type" are supposed to be locked in non-active. This works.
   • "Archived" and "Status" are empty, as they do not exist in current. This also works.
   • Depending on the "Type", only certain of the additional attributes are shown on edit. This works as well.
   • I would also like "Status" to have some influence on how certain other attributes are preset and/or shown. This is where the problem starts...
2. Edit the entry in current.
   • As expected, "Created" and "Type" are shown as locked.
   • As soon as I change the selector for "State", the whole edit mask is redrawn - and the date shown in "Created" is deleted.

I've been experimenting with this quite a while and as far as can see the following applies:

• Only date format attributes are affected
• Only locked attributes seem to be deleted completely
• If I have a date attribute that is not locked and I set it partially in the edit mask (e.g. only select the month or enter a year), it is also deleted
• If I have a date attribute that is not locked and I set it completely in the edit mask (i.e. day, month and year), it is not deleted

During the experiments I came up with a stripped down version of the non-active logbook configuration, which does show the bug. It only contains Type, Created, Status, Archived. To make an entry to experiment, you'll have to comment out the "Locked attributes" line, make a new entry (with "Created" date), the uncomment that line.

I hope my description isn't too confusing - please don't hesitate to ask if anything is unclear. I'd be much obliged if you saw a chance to fix this at some point...

Best regards,

Thomas

Hello friends, 

Exist some form to increase limits of items (100) in the Options List



Thanks for any help

Hi :)

First i have to say that i love this exelent program,

and that it saved me Hours of trouble using it ^^

Thanks Stefan Ritt :)

Now.. here is my problem :P

1. I was wondering if there is a possibility to have separate 'Options Category'..  One for Admin and one for User?

    If it is possible, can i have an example?

2. How can i arrange pictures in the main window, f.eks 1 picture in center, to the right or wherever i want?

Regards

Kim R

Hello,
    Is it possible to have a drop down list with commas in the options.  
For instance, if you want to have a attribute "CityState" you would 
probably want a comma between the City and State name.  Since the Options 
are separated by commas, it turns into two different options.  I dont know 
if there is a way to do this or if this is a bug?

MO

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?

Hi,

I use the following attribute definition:

Options <attribute> = <list> 

However, I am being limited by the list length limit of 100. I have 103 items, but I only see 100.

Could the limit be extended (to 200 for instance) ?

Thanks a lot for your help

Soren