> I needed the export feature and could not find documentation on it in the latest 
> version. I finally read the code and added Find Menu Text = <filename>
> where filename had the tags XML, CSV1, and CSV2
> This always exports all records. Shouldn't it just export the records appearing in 
> the window?

Exporting workes as follows: Click on "Find", and switch the radio button to XML or CSV.
If you click on "Search", you will be prompted where to save the resulting "export.xml"
or "export.csv". I did this through the search page because you can then specify som
filters, in order not to export all records.

> (BTW, the XML export is not valid. Internet Explorer complains about the first line)

The XML charset in the first line was missing. I fixed that, new version under CVS. Or
you can manually change the first line to

<?xml version="1.0" encoding="ISO-8859-1"?>

> > I needed the export feature and could not find documentation on it in the latest 
> > version. I finally read the code and added Find Menu Text = <filename>
> > where filename had the tags XML, CSV1, and CSV2
> > This always exports all records. Shouldn't it just export the records appearing in 
> > the window?
> 
> Exporting workes as follows: Click on "Find", and switch the radio button to XML or CSV.
> If you click on "Search", you will be prompted where to save the resulting "export.xml"
> or "export.csv". I did this through the search page because you can then specify som
> filters, in order not to export all records.
> 
> > (BTW, the XML export is not valid. Internet Explorer complains about the first line)
> 
> The XML charset in the first line was missing. I fixed that, new version under CVS. Or
> you can manually change the first line to
> 
> <?xml version="1.0" encoding="ISO-8859-1"?>

Thanks much!! I can't believe I missed seeing those options. Works great. (There is a 
danger to having the source code. You tend to read it instead of looking at the way the 
program works )

BTW,
Is there any way to turn off the Text column at the right side of the list?

> BTW,
> Is there any way to turn off the Text column at the right side of the list?

Summary lines = 0

Have tried to use "Menu commands =" to list menu commands available as per:
"Menu commands = List, Back, New, Edit, Delete, Find, Config, HELP, Logout"

but it does not seem to work; with command above I get default menu 
structure.

Using:
"Find Menu commands = List, Back, New, Edit, Find, Delete, Config, Logout, 
HELP"

I get the menu I want.
Q what's the difference?????

> Have tried to use "Menu commands =" to list menu commands available as per:
> "Menu commands = List, Back, New, Edit, Delete, Find, Config, HELP, Logout"
> 
> but it does not seem to work; with command above I get default menu 
> structure.
> 
> Using:
> "Find Menu commands = List, Back, New, Edit, Find, Delete, Config, Logout, 
> HELP"
> 
> I get the menu I want.
> Q what's the difference?????

"Find menu commands" apply to the LIST of entries, while "Menu commands" apply
to the page where a SINGLE entry is shown. I know that "Find menu commands" is
a misleading name, but it's historical, I should change it to "Menu commands"
and change the other to "Entry menu commands", does that make more sense?

> > Is there any way to configure elog so that attribute fields can be edited 
> > on more than line like the 'text' field? 
> > 
> > (This would be useful so that attributes could contain larger portions of 
> > text including line breaks)
> 
> No, but this request is already on the wishlist
> (http://midas.psi.ch/elog/wishlist.html) since some time. I added your vote.

Stefan,

Was just wondering about the status of the multi-line attributes in Elog, are 
they implemented in elog yet? If not is that something you are planning to do 
in the future?

many thanks

Paul

> Was just wondering about the status of the multi-line attributes in Elog, are 
> they implemented in elog yet? If not is that something you are planning to do 
> in the future?

In order to have multi-line attributes, the whole format of the logbooks has to be
changed. I plan to use XML for the logbook format in the future. We would not have
any more one file per day, but one big file per logbook. I have already some XML
functionality in elog, but this one requires a major rewrite of the whole code. On
the other hand, searching etc. will become much faster afterwards. I plan to start
this development soon, but it might take quite some time, so don't expect it
before summer or fall.

Best regards,

  Stefan

> > Was just wondering about the status of the multi-line attributes in Elog, are 
> > they implemented in elog yet? If not is that something you are planning to do 
> > in the future?
> 
> In order to have multi-line attributes, the whole format of the logbooks has to be
> changed. I plan to use XML for the logbook format in the future. We would not have
> any more one file per day, but one big file per logbook. I have already some XML
> functionality in elog, but this one requires a major rewrite of the whole code. On
> the other hand, searching etc. will become much faster afterwards. I plan to start
> this development soon, but it might take quite some time, so don't expect it
> before summer or fall.
> 
> Best regards,
> 
>   Stefan

Thanks for your help, thats useful to know.

Paul