Re: Possible Formatting bug: Summary view, posted by Steve Jones on Fri Jul 16 04:37:47 2004
|
> > A temporary fix for this is to set summary lines = 0
>
> Right, that's the only way. I would call this "permanent fix" (;-)
|
Date format problem in "Thread display = ", posted by Steve Jones on Fri Jul 16 16:53:01 2004
|
I have an attributes defined as:
- Attributes = Author, PlannedDate, FunctionalArea, Operation, Category,
|
|
BUG?: Preset text = causes replication of text when re-editing a logbook entry., posted by Steve Jones on Fri Jul 16 19:06:35 2004
|
With the "Preset text = " specified, when re-editing a logbook entry (say to
correct a spelling error) the text of the "Message" is replicated and placed
directly below the original text.
|
|
Bugs in newer updates w/ Debian install?, posted by Todd Corsa on Thu Jul 22 16:50:19 2004
|
I just updated ELOG using the latest elogd.c, and now my Quick Filters seem
to stop working after the first or second filter attempt. I find that if I
allow fewer quick filter options it seems to work more consistently. For
|
|
List Dispaly produces wrong output in 2.5.3 built 23.7.04 (snapshot), posted by Ulrich Trüssel on Tue Jul 27 17:56:56 2004
|
I did not have the following problem in any snapshot before 23.7.04 .
Actually I do not have a possibility to test the snapshot under an other
system than win xp pro sp 1 (fully pached).
|
Re: List Dispaly produces wrong output in 2.5.3 built 23.7.04 (snapshot), posted by Stefan Ritt on Wed Jul 28 14:17:25 2004
|
> Using "List Display = <attributes>" produces an ususal output with the text
> field content in the first row and a row title of the first 3 letters.
|
|
Re: List Dispaly produces wrong output in 2.5.3 built 23.7.04 (snapshot), posted by Ulrich Trüssel on Wed Jul 28 16:13:04 2004
|
Thank you very much Stefan!!!
Also the horizontal alignement with "Format = 1" looks much better as before
|
|
getcfg problem in v1.410: Truncation of long config strings, posted by Steve Jones on Wed Jul 28 18:25:32 2004
|
Just compiled 1.410 and have run into an issue that *may* have been
introduced in 1.393.
|