Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 650 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  66653   Thu Dec 10 19:06:18 2009 Reply Stefan Rittstefan.ritt@psi.chBug reportWindows2.7.7 2246Re: 2.7.6 and 2.7.7 crash upon opening logbook that runs on 2.7.5

David Spindler wrote:

 

 Ok, I am now assuming the offending log file has been removed. Correct?

No, you never submitted any file. It was missing in all your posts. In worst case send it by email to me. 

  1558   Wed Dec 21 20:39:52 2005 Reply Stefan Rittstefan.ritt@psi.chInfo  Re: 2.6.0-bata5

Carl Shirey wrote:
Do you have 2.6.0-bata5 for linux as setup for RPM install. I was able to locate the version for windows but not for linux.
Thanks for your help.


There is a 2.6.0 out by now.
  65945   Fri Aug 8 14:20:27 2008 Reply Yoshio ImaiQuestionAll2.7.4xRe: 2 questions :: different colors in list view based on "type" + change verbage of "type"

dale cooper wrote:
I'd love to display in the LIST VIEW (full, summary, or threaded views) different color's based on which TYPE was selected...

You can achieve this by using a "style" directive for this attribute. E.g. if your attribute is called "Shift" and entries with value "Day" should be green, value "Swing" should be blue, you should add
Style Shift Day = background-color:green
Style Shift Swing = background-color:blue
(and so on) to the config file.



Quote:
really I am just wondering if I can change the verbage that ELOG is using for the term TYPE? Is that doable?

As long as I am not missing a key point in your problem, you should be able to define the names of your logbook attributes simply with the "Attribute" directive. So, if you want the users to enter the shift and the name of the shift leader, you would put a line
Attributes = Shift, Shift leader
Options Shift = Day, Swing, ... <and so on>
Options Shift leader = Mike, Edward, John, ... <and so on>
and the logbook display should correctly show "Shift" and "Shift leader" in the header line of each entry ...
  65948   Mon Aug 11 06:56:56 2008 Reply dale cooperagentdcooper@gmail.comQuestionAll2.7.4xRe: 2 questions :: different colors in list view based on "type" + change verbage of "type"
PERFECT, you answered my questions EXACTLY with what I am looking for! thanks soo much!
agentdcooper


Yoshio Imai wrote:

dale cooper wrote:
I'd love to display in the LIST VIEW (full, summary, or threaded views) different color's based on which TYPE was selected...

You can achieve this by using a "style" directive for this attribute. E.g. if your attribute is called "Shift" and entries with value "Day" should be green, value "Swing" should be blue, you should add
Style Shift Day = background-color:green
Style Shift Swing = background-color:blue
(and so on) to the config file.



Quote:
really I am just wondering if I can change the verbage that ELOG is using for the term TYPE? Is that doable?

As long as I am not missing a key point in your problem, you should be able to define the names of your logbook attributes simply with the "Attribute" directive. So, if you want the users to enter the shift and the name of the shift leader, you would put a line
Attributes = Shift, Shift leader
Options Shift = Day, Swing, ... <and so on>
Options Shift leader = Mike, Edward, John, ... <and so on>
and the logbook display should correctly show "Shift" and "Shift leader" in the header line of each entry ...
  981   Mon Mar 14 21:00:57 2005 Reply Stefan Rittstefan.ritt@psi.ch   Re: 2 Extendable options when created new entries
I fixed this problem in revision 1.586. It will be contained in the next release.
  473   Fri Feb 13 21:52:48 2004 Reply Stefan Rittstefan.ritt@psi.ch Linux2.5.0Re: -W -Wall options (using gcc)
Thanks, I did so.
  475   Mon Feb 16 16:07:34 2004 Question Stefan Rittstefan.ritt@psi.ch Linux2.5.0Re: -W -Wall options (using gcc)
So I fixed all compiler generated warnigns except these:

[midas@pc2075 ~/elog]$ gcc -g -O -W -Wall -o elogd src/elogd.c
src/elogd.c: In function `set_cookie':
src/elogd.c:4675: warning: `%y' yields only last 2 digits of year
src/elogd.c: In function `send_file_direct':
src/elogd.c:5483: warning: `%y' yields only last 2 digits of year
src/elogd.c: In function `show_elog_list':
src/elogd.c:11938: warning: `%x' yields only last 2 digits of year in some 
locales
src/elogd.c:11957: warning: `%x' yields only last 2 digits of year in some 
locales
src/elogd.c:11979: warning: `%x' yields only last 2 digits of year in some 
locales
src/elogd.c:11987: warning: `%x' yields only last 2 digits of year in some 
locales
src/elogd.c: In function `ctrlc_handler':
src/elogd.c:15864: warning: empty body in an if-statement
src/elogd.c: In function `hup_handler':
src/elogd.c:15870: warning: empty body in an if-statement

Do you know how to disable these warnings or any other workaround? I would 
like to compile without any remaining warnings.
  476   Mon Feb 16 16:40:50 2004 Question Heiko Scheith.scheit@mpi-hd.mpg.de Linux2.5.0Re: -W -Wall options (using gcc)
> So I fixed all compiler generated warnigns except these:
> 
> [midas@pc2075 ~/elog]$ gcc -g -O -W -Wall -o elogd src/elogd.c
> src/elogd.c: In function `set_cookie':
> src/elogd.c:4675: warning: `%y' yields only last 2 digits of year
> src/elogd.c: In function `send_file_direct':
> src/elogd.c:5483: warning: `%y' yields only last 2 digits of year
> src/elogd.c: In function `show_elog_list':
> src/elogd.c:11938: warning: `%x' yields only last 2 digits of year in some 
> locales
> src/elogd.c:11957: warning: `%x' yields only last 2 digits of year in some 
> locales
> src/elogd.c:11979: warning: `%x' yields only last 2 digits of year in some 
> locales
> src/elogd.c:11987: warning: `%x' yields only last 2 digits of year in some 
> locales
> src/elogd.c: In function `ctrlc_handler':
> src/elogd.c:15864: warning: empty body in an if-statement
> src/elogd.c: In function `hup_handler':
> src/elogd.c:15870: warning: empty body in an if-statement
> 
> Do you know how to disable these warnings or any other workaround? I would 
> like to compile without any remaining warnings.


Have a look at the gcc info pages:

$ info gcc "invoking gcc" "warning options"
ELOG V3.1.5-3fb85fa6