ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
67303
|
Fri Jul 13 17:09:58 2012 |
| Richard Stamper | richard.stamper@stfc.ac.uk | Question | All | 2.9.2 | Re: Number of conditional attributes |
Stefan Ritt wrote: |
Richard Stamper wrote: |
Is there a limit on the number of conditions that can be simultaneously active in a log? When I activate more than 10 conditions I start to see side effects with other conditions being deactivated. I think this is due to the hard-coded array size of 10 for clist in the match_param function in elogd.c. If so, could this limit be increased?
Are there other limits on the number of conditions, or the length of condition names? If I've understood the code right, the _condition string holds a comma-separated list of the active conditions, so the 256 byte length of this will also put some limit on the number of conditions that can be active.
|
Ups. I never imagined that someone would use more than 10 conditions. I'm not 100% sure if the problem is the clist array, but can you try to set it to 20 and see if it gets better? You can also send me your config file and I can try it myself.
|
I'll try increasing the list size(s), and will also prepare a simplified config file for you to look at. Maybe there is a another way to implement what I am trying to achieve?
In general terms I am trying to give an e-log a "memory" of what has been recorded previously in order to constrain what is permissible to record next. I do this by starting a log with an initial entry, then alter the config so that users can add records only by duplicating the last record. The log records the current state of some variables, and allows users to record changes to the state of any of these variables. Conditions are used to constrain the permitted state changes, depending on the current state; conditions are also used, with subst options, to update the current state variables when changes are made.
Specifically, we have "Mate-Demate" logs for connectors to record when connectors are mated and demated. Previously we just had an attribute for each connector in an assembly with options "Mate", "Demate" and "-" to indicate that either a mate or demate was carried out or that the connector was not touched on this occasion (although others were). My cunning plan was to ensure that a "Demate" (or no-op) was possible only if the connector is currently mated, and conversely that a "Mate" (or no-op) was possible only if the connector is currently demated. For each connector (e.g. ConnectorA), there are now two attributes
- "ConnectorA state", to record the current state, and
- "ConnectorA" to record any change.
A new record can be created only by duplicating the last record, thus copying the current state of the connectors, and for each connector the relevant config file entries are like this:
Show Attributes = ConnectorA
Show Attributes Edit = ConnectorA state, ConnectorA
Locked Attributes = ConnectorA state
Preset on duplicate ConnectorA = -
Options ConnectorA state = Mate{1}, Demate{2}
{2} Options ConnectorA = -, Mate{3}
{1} Options ConnectorA = -, Demate{3}
{3} Subst ConnectorA state = $ConnectorA
The logbook is set up with a record with "ConnectorA state" set to "Demate", which constrains "ConnectorA" to record either a no-op or a mate; if a mate is subsequently recorded then the Subst option for "ConnectorA state" substitutes the new status ("Mate") for the connector before the record is saved; in the new last record "ConnectorA state" is now set to "Mate" which permits only a demate; when a no-op is selected the state is unchanged, having been inherited through duplication from the last record. The number of conditions used is one per "ConnectorX state" attribute, plus one for each connector whose state is changed, so for assemblies with more than 5 connectors it is possible to have more than 10 conditions active at once.
|
67336
|
Sun Sep 16 18:40:06 2012 |
| Josef Uher | josef.uher@gmail.com | Question | All | 2.9.2 | HTML editor | Hi All,
maybe I missed something in the configuration, but how do I get this nice editor for HTML like the one available on this forum?
Thanks a lot for advice. |
67338
|
Mon Sep 17 09:16:38 2012 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Question | All | 2.9.2 | Re: HTML editor |
Josef Uher wrote: |
[...] maybe I missed something in the configuration, but how do I get this nice editor for HTML like the one available on this forum?[...]
|
The fckeditor is already installed with the elog package. All you need to do is to enable HTML in ELOG and Javascript in your browser.
The ELOG command "Allowed encoding = 7" gives you the same encoding choices as in this forum. |
67340
|
Mon Sep 17 15:14:46 2012 |
| Josef Uher | josef.uher@gmail.com | Question | All | 2.9.2 | Re: HTML editor |
Andreas Luedeke wrote: |
Josef Uher wrote: |
[...] maybe I missed something in the configuration, but how do I get this nice editor for HTML like the one available on this forum?[...]
|
The fckeditor is already installed with the elog package. All you need to do is to enable HTML in ELOG and Javascript in your browser.
The ELOG command "Allowed encoding = 7" gives you the same encoding choices as in this forum.
|
Hi Andreas, thank you for your reply. I have already found out that the problem on Mac was that I moved the cfg file to some other folder which did not contain the resources and scripts. I used the "-s" switch and now it works nicely. However, now I try to do the same thing on Windows and even the "-s" switch does not help (the default encodings etc. are set in the cfg file). I compiled the elog on Mac, but I used the installation package on Windows. |
67408
|
Thu Dec 27 01:33:11 2012 |
| Valentin | Valentin.Kozlov@kit.edu | Question | All | 2.92 | How to put "Quote text" _below_ new message? | Hi there,
It seems that by default in a message created as "reply" of another message, the "quoted text" of the original entry is put at the _TOP_ of the new entry and not movable (Firefox 17, elog 2.92). I would strongly like to have it opposite, i.e. that one is able to create a new text first and only then has the "quoted text" since people are interested to see a new information and only then the previous messages as sort of "reminder". It was like this in older (2.6?) version but now I did not find how to change this default behavior. Did I miss something?
Cheers
Valentin |
67409
|
Thu Dec 27 12:52:00 2012 |
| David Pilgram | David.Pilgram@epost.org.uk | Question | All | 2.92 | Re: How to put "Quote text" _below_ new message? |
Valentin wrote: |
Hi there,
It seems that by default in a message created as "reply" of another message, the "quoted text" of the original entry is put at the _TOP_ of the new entry and not movable (Firefox 17, elog 2.92). I would strongly like to have it opposite, i.e. that one is able to create a new text first and only then has the "quoted text" since people are interested to see a new information and only then the previous messages as sort of "reminder". It was like this in older (2.6?) version but now I did not find how to change this default behavior. Did I miss something?
Cheers
Valentin
|
I use plain encoding, cannot answer for the others but it should do the trick as it's in the documentation. I'm using Firefox some large number and 2.9.2.-2475
I do what I believe you want, and get it by having the following line in my config file for that logbook (which is part of elog.cfg):
Prepend on reply = \n
This gives a blank line at the "top" of the entries when you start a reply, and all the previous entries gain another "> " unless you've also altered that default behaviou (as in fact I have). The result then looks like:
Latest line of text
> Previous entry
> > Previous entry to that |
67415
|
Mon Jan 7 16:43:27 2013 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | 2.92 | Re: How to put "Quote text" _below_ new message? | If you use HTML encoding, you can do that with
Prepend on reply = <br />
to achieve the same thing (as I did just here in this reply).
Stefan
David Pilgram wrote: |
Valentin wrote: |
Hi there,
It seems that by default in a message created as "reply" of another message, the "quoted text" of the original entry is put at the _TOP_ of the new entry and not movable (Firefox 17, elog 2.92). I would strongly like to have it opposite, i.e. that one is able to create a new text first and only then has the "quoted text" since people are interested to see a new information and only then the previous messages as sort of "reminder". It was like this in older (2.6?) version but now I did not find how to change this default behavior. Did I miss something?
Cheers
Valentin
|
I use plain encoding, cannot answer for the others but it should do the trick as it's in the documentation. I'm using Firefox some large number and 2.9.2.-2475
I do what I believe you want, and get it by having the following line in my config file for that logbook (which is part of elog.cfg):
Prepend on reply = \n
This gives a blank line at the "top" of the entries when you start a reply, and all the previous entries gain another "> " unless you've also altered that default behaviou (as in fact I have). The result then looks like:
Latest line of text
> Previous entry
> > Previous entry to that
|
|
67518
|
Fri May 31 11:41:48 2013 |
| Andreas Luedeke | andreas.luedeke@psi.ch | Bug fix | All | 2.9.2-2481 | Re: Export entries to XLS or CSV? |
Jim Tinlin wrote: |
Andreas Luedeke wrote: |
scogordo wrote: |
I've been asked to export one of our logbooks to xls or csv. Doable?
Thanks,
Scott
|
Hi Scott,
yes, every user can export entries using the "find" command.
Just select the export format in the first line
Export to:
  ⇄
Detect language » English
I often use the XML Format, but CSV is fine if you just want to import the entries to some spreadsheet program.
I was shocked to find out that this feature has not yet made it into the documentation?!? But it is that simple to use that there is not much to document.
There is even an "Import" command, to reimport entries from a file. But this is tricky to use: if you have fields of type date or datetime, then you have to convert those fields in the proper format.
|
I tried EXPORTING logbooks as .csv but have not been fully successful. Elog seems to only export the data entered for various fields with the exception of the text field.
Here is an example export from my logbook (used to track simulator problems), I would like to also export the TEXT field so it can be used by my managers in excel...but as you can see there is no entry for "TEXT" fields...
Thanks in advance!
"Message ID","Date","Author","Type","Status","Priority"
107,Thu 30 May 2013 11:28:57 -0700,"Jim Tinlin","Graphic Display","Evaluated","Low"
106,Thu 30 May 2013 10:02:24 -0700,"Jim Tinlin","Graphic Display","Identified","Low"
105,Thu 30 May 2013 08:07:27 -0700,"Jim Tinlin","Problem ID","Identified","Medium"
104,Thu 30 May 2013 08:04:30 -0700,"Jim Tinlin","Problem ID","Identified","Medium"
103,Wed 29 May 2013 09:36:11 -0700,"Jim Tinlin","Problem ID","Evaluated","High"
102,Wed 29 May 2013 08:58:02 -0700,"Jim Tinlin","Problem ID","Evaluated","High"
|
Yes, you're right: the text field is only exported in XML and Raw mode.
It is questionable how EXCEL should cope with HTML or ELCode output from the text fields.
But I admit that this would be a useful feature for logbooks that only use plain text entries. And it is simple to implement.
I've attached a patch to elogd.c from elog-2.9.2-2081 that adds a third CVS mode 'CSV (";" separated) + Text'.
(This string has not yet been added to the localization.)
As far as I've tested it works fine to import the text to OpenOffice and EXCEL, even with multiple text lines and HTML code in the text.
Of course the spreadsheet programs just display the HTML source.
Stefan, do you think this should be added to the official branch?
 ⇄
Detect language » English
⇄
Detect language » English
|
Attachment 1: diff.txt
|
11645,11650d11644
< if (strieq(mode, "CSV3"))
< rsprintf("<input type=radio id=\"CSV3\" name=\"mode\" value=\"CSV3\" checked>");
< else
< rsprintf("<input type=radio id=\"CSV3\" name=\"mode\" value=\"CSV3\">");
< rsprintf("<label for=\"CSV3\">%s </label>\n", loc("CSV (\";\" separated) + Text"));
<
19535c19529
< csv = strieq(mode, "CSV1") || strieq(mode, "CSV2") || strieq(mode, "CSV3");
---
> csv = strieq(mode, "CSV1") || strieq(mode, "CSV2");
20266,20268c20260
< } else {
< if (strieq(mode, "CSV3"))
< rsprintf(";\"Text\"");
---
> } else
20270d20261
< }
20973,20987c20964
< } else {
< if (strlen(text)>0 && strieq(mode, "CSV3")) {
< rsprintf(";");
< strlcpy(str, text, sizeof(str));
< rsputs("\"");
< pt1 = str;
< while ((pt2 = strchr(pt1, '"')) != NULL) {
< *pt2 = 0;
< rsputs(pt1);
< rsputs("\"\"");
< pt1 = pt2 + 1;
< }
< rsputs(pt1);
< rsputs("\"");
< }
---
> } else
20989d20965
< }
|
|