ELOG Forum

I have done the changes to my logbock, but I think I have done something wrong. As an example, the window where you write in your note is not sized anymore like before. I have to scroll a lot to the right to see the right border of the window.

The only thing I have done was try to delete: the OS: Linux Window Mac OSC All Other info.

How should I know what you have done wrong if you don't tell me. It's like if you call your PC manufacturer and tell him: "My PC is not working, what is wrong?". So please send me your elogd.cfg, and make a few screen shots so that I know what is going on.

66843

Tue Jun 8 23:08:41 2010

Re: change design part of the discussion board

Stefan Ritt wrote:

Heinzmann wrote:

Hello Stefan,

If I would like to change the design of the attached part of the discussion board like:

deleting OS: (including blue box) Linux Windows Mac OSX All Other (including green box)

Where and how could I do this?

Thank you

Well, the official forum at midas.psi.ch cannot be changed by you. But if you installed a local logbook similar to the one here, you simple go and edit the confitguration file elogd.cfg. Please read the documentation for further information.

Stefan,

The only thing I have done was try to delete: the OS: Linux Window Mac OSC All Other info.

Please could you help me out?

66842

Tue Jun 8 16:33:07 2010

Yoshio Imai wrote:

Sometimes, it is annoying that the

[code]

-Tag creates a line break, because there are situations where verbatim text inside the regular text flow is desirable (just like here). I would like to request an additional elcode-tag

[ilcode]

(in-line code) which translates to

<code>

instead of

<pre>

.

Yoshio

The [code] tags produce <pre>...</pre> tags for multi-line listings, where several spaces should not be dropped to keep the formatting of some source code for example. I also want it sometimes in a single line, so what I do is to use a [FONT=Courier New] tag, which produces output very similar to <code>, but without line breaks.

66841

Tue Jun 8 15:48:06 2010

Hi, Stefan!

Sometimes, it is annoying that the

[code]

-Tag creates a line break, because there are situations where verbatim text inside the regular text flow is desirable (just like here). I would like to request an additional elcode-tag

[ilcode]

(in-line code) which translates to

<code>

instead of

<pre>

.

Cheers

Yoshio

66840

Tue Jun 8 12:02:36 2010

Re: Restricting logbook view

Allen wrote:

Is there anyway to restrict access so that a user can only see the log entries they post or only replies to their log entry? I know it is possible to restrict editing to only posts they submitted, but I have a need to not even allow them to see other posts except for what they submitted and I am wondering if this is possible currently, or if this is planned, or could be planned for a future version?

No, this is not possible at the moment. As a workaround you could define one logbook per user, then restrict the user access to the individual logbooks. Of course this only makes sense if there are not too many users.

66839

Tue Jun 8 09:53:09 2010

Re: alphabetize Quick Filter items?

Dennis Seitz wrote:

Stefan Ritt wrote:

Dennis Seitz wrote:

Stefan Ritt wrote:

Dennis Seitz wrote:

Hi Stefan,

I'd like to request a feature: automatic alphabetization of the items in the Quick Filter menus.

We track quite a few detector assemblies, which are produced with non-sequential designations. It would be useful if the Quick Filter list was automatically sorted alphabetically to make it more convenient for folks to find a particular item.

I know people can always search by designation but it would be handy to have this alpha sorting feature. Would it be possible to include that in a future release?

Thanks again for a *very* useful logging system!

Dennis

The order of items in a Quick Filter menu is exactly as in the configuration file. Like if you have items

Options Type = C, D, A, B

they are shown like that in the quick filter menu. If you want to sort them, just do the sorting yourself in the configuration file like

Options Type = A, B, C, D

I have not implemented automatic sorting since some people want a different order, like some main topics at top. So by following the order from the configuration file, everybody can be satisfied just by chaning the order in the config file.

- Stefan

Yes, I have been manually sorting and resorting. We have extendable attributes and the list keeps growing so I have to resort every so often. I thought perhaps a simple alphanumeric sort as an option would be popular with most users so I thought I'd ask for it. It would really simplify things for me. Users who want to sort manually could do so by disabling the option. It never hurts to ask!

Ok, I implemented

Sort attribute options = 1

in the current SVN revision.

I've tried adding this statement to my cfg file but the attributes are still unsorted in the QuickFilter menus. Was this implemented in 2.7.7?

Shouldn't an existing configuration file entry like

Options Type = C, D, A, B

be sorted in the QuickFilter menu as A B C D?

You need revision 2252 or later. So you have to upgrade to 2.7.8.

Goto page Previous 1, 2, 3 ... 371, 372, 373 ... 806, 807, 808 Next

ELOG V3.1.5-3fb85fa6