ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
605
|
Wed Jul 14 22:59:05 2004 |
| Steve Jones | steve.jones@freescale.com | Question | All | 2.5.3 | Re: Question on how "Format <attribute> = " works |
> Just have a look at elog:571 which should answer your question. Also look at
> elog:Config+Examples/4 which is the configuration of this Forum (which as you can
> see has all attributes in a single line, even using different fonts).
Ok, I think I see now. I was assuming it applied to the entry form as well.
Thanks! |
606
|
Thu Jul 15 09:44:08 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | All | 2.5.3 | Re: Possible Formatting bug: Summary view |
> A temporary fix for this is to set summary lines = 0
Right, that's the only way. I would call this "permanent fix" (;-) |
607
|
Thu Jul 15 10:01:03 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | All | 2.5.3 | Re: Wishlist: TOOLTIP for ATTRIBUTES |
Ok, I added the option
Tooltip <attribute> = ...
I apply the HTML "title" tag to the whole table row, so the tooltip appears on the
whole line, not only the attribute name. I guess this is much more intuitive. Give
it a try. New version under CVS and available as a snapshot. |
608
|
Thu Jul 15 21:21:50 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | 2.5.3 | Re: Question on how "Format <attribute> = " works |
> Ok, I think I see now. I was assuming it applied to the entry form as well.
Well, good idea. I implemented that. Have a look at this forum (just hit reply to this
entry) and you'll see it. I'm not completely happy with it (at least on small 1024x768
screens), but it's configurable anyhow. New version under CVS. |
610
|
Fri Jul 16 04:36:51 2004 |
| Steve Jones | steve.jones@freescale.com | Question | All | 2.5.3 | Re: Question on how "Format <attribute> = " works |
> > Ok, I think I see now. I was assuming it applied to the entry form as well.
>
> Well, good idea. I implemented that. Have a look at this forum (just hit reply to this
> entry) and you'll see it. I'm not completely happy with it (at least on small 1024x768
> screens), but it's configurable anyhow. New version under CVS.
Now that creates an interesting display - especially with the icons and radio buttons.
But it works!
Thanks. |
611
|
Fri Jul 16 04:37:47 2004 |
| Steve Jones | steve.jones@freescale.com | Bug report | All | 2.5.3 | Re: Possible Formatting bug: Summary view |
> > A temporary fix for this is to set summary lines = 0
>
> Right, that's the only way. I would call this "permanent fix" (;-)
I would too - and it actually produces the output that I wanted to see anyway.
Thanks! |
613
|
Fri Jul 16 16:53:01 2004 |
| Steve Jones | steve.jones@freescale.com | Bug report | All | 2.5.3 | Date format problem in "Thread display = " |
I have an attributes defined as:
- Attributes = Author, PlannedDate, FunctionalArea, Operation, Category,
HardwareName, Significance, EmailNotify, LastRevision, Subject
I have PlannedDate defined as:
- Type PlannedDate = date
When I use the following statement:
- Thread display = $subject, planned for $PlannedDate. Last revised:
$lastrevision
I get the following in my THREADED logbook view:
"Adding new services, planned for 1090519200. Last revised: Thu Jul 15
18:03:52 2004"
Note that the ATTRIBUTE $PlannedDate prints as a (I am guessing) serialized
date and is not formatted.
I'm not sure if this is manifested elsewhere. |
614
|
Fri Jul 16 17:51:52 2004 |
| Steve Jones | steve.jones@freescale.com | Request | All | 2.5.3 | WISHLIST: Type <attribute> = user |
Something to add to the wishlist:
- Type <attribute> = user
This would define an attribute as being of the type "user" which is a list
of login id's as defined in a password file or on the "Login user =" line.
In a dataentry form the presence of this ATTRIBUTE would result in a
picklist of loginid's and/or fullnames. |