ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
621
|
Wed Jul 28 14:17:25 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Windows | 2.5.3 snap | Re: List Dispaly produces wrong output in 2.5.3 built 23.7.04 (snapshot) |
> 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.
I fixed that problem. Please get the snapshot from July 28th 14:16. |
620
|
Wed Jul 28 14:14:05 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.5.3 | Re: Author field on reply |
> I followed copied the example config provide to run on my server .
> Apparently , the author field was blank when i do a reply .
> I was hoping to get it to be the actual reply author.
> Just like the way the forum is done up.
> Please help ..
This (new) behaviour came from the request that some people id *NOT* want to
have the new author on the reply, but the *ORIGINAL* (they used an attribute
"Origial author" which should not be replaced on a reply). Therefor I added a
new option to resolve that. So please use
Preset Author = $long_name
Preset on reply Author = $long_name
if you want to have the attribut "Author" replaced by the current one both on
new entries and on replies. |
619
|
Tue Jul 27 18:33:52 2004 |
| Fred Hooper | fhooper@sushisoft.com | Bug fix | Linux | 2.5.3 | speeding up elog : gcc compile optimizations |
Elog is a great program, but it can be slow.
I noticed that the gcc compiler options in the tarball Makefile were not
conducive to speed. There, I tried changing the gcc options to:
CFLAGS = -O3 -funroll-loops -fomit-frame-pointer -W -Wall
for version 2.5.3, the compile worked, and the program appears to work as
normal, but a bit faster. I have not benchmarked it, but I think it should
offer a nominal increase in speed.
In particular, I removed the "-g" profiling option, which is not needed for
production code, and can be safely removed. In addition, I put in slightly
aggressive optimization settings, so if this doesn't work for you, you can
first try removing the -f setting, and then backing off the optimization to -O2.
Other may want to post other settings that work for them. |
618
|
Tue Jul 27 17:56:56 2004 |
| Ulrich Trüssel | ulrich.truessel@familienhund.ch | Bug report | Windows | 2.5.3 snap | List Dispaly produces wrong output in 2.5.3 built 23.7.04 (snapshot) |
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).
Using my logbooks as well as the demo logbook works well under older
snapsgots of 2.5.3 as well as long as the "List Display = <attributes>" is
not used!
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.
Ex.:
Attributes = Customername, Customeraddres
List Display = Customername, Customeraddres
Output:
¦Cus¦Customeraddres¦
If no record is in the logbook, only the "Cus" is dispalyed! Removing "List
Display = <attributes>" produces a normal output with same logbook!
By the way: Thnak's for the Format in the entry/edit view!!! |
617
|
Thu Jul 22 16:50:19 2004 |
| Todd Corsa | tcorsa@bnl.gov | Bug report | Linux | 2.5.3 | Bugs in newer updates w/ Debian install? |
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
example:
Example 1-
Quick filter = Date
The date filter will work without a problem no matter how many times I use
it.
Example 2-
Quick filter = Date, Category, Status, Priority
The first filter I use will work, but upon trying a new filter, or just a
new option in the same filter, all options return to "All Entries" and no
filter options have any effect on the view.
If I exit the log book, and come back in, it works for the first filter
attempt, then stops again.
This used to work fine prior to the update. I should also mention that the
original installation of ELOG was from the Debian package. At that point,
nothing was where the documentation said it should be (e.g. elogd.cfg was
called elog.conf and was placed in the /etc/ directory). Everything worked
fine, so I left it alone. When I recompiled with the newer elogd.c,
anything that required a path was hosed, so I now have to specify the
resource directory and the path to the conf file when starting ELOG. I
don't know why this would affect the Quick Filter, and I'd assume that it
would just stop working all together. Also, when I recompiled using "gcc -
O -o elogd elogd.c", I received the following warning:
elogd.c:546: warning: conflicting types for built-in function `logf'
Any suggestions?
Thanks!
Todd |
616
|
Mon Jul 19 06:07:54 2004 |
| Geo Geo | gorilla_geo@yahoo.com | Question | Windows | 2.5.3 | Author field on reply |
Hi
I followed copied the example config provide to run on my server .
Apparently , the author field was blank when i do a reply .
I was hoping to get it to be the actual reply author.
Just like the way the forum is done up.
Please help ..
Are you using Remove on reply option ?
regards |
615
|
Fri Jul 16 19:06:35 2004 |
| Steve Jones | steve.jones@freescale.com | Bug report | All | 2.5.3 | BUG?: Preset text = causes replication of text when re-editing a logbook entry. |
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.
Commenting out the "Preset text = " line prevents this behavior. this
occurs under both FireFox and IE6.0 clients. |
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. |