ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
1123
|
Mon May 2 14:51:43 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | All | | Re: per entry "expand" in threaded view |
> ok, i've downgraded my request then ...
>
> it will be still useful to have the possibility of expland selectively a single thread :-)
That you can do by clicking on the thread and look at the thread at the top of the page (;-))
That's exactly the same number of clicks as you would need to expand a thread (:-))) |
1125
|
Mon May 2 15:37:11 2005 |
| Emiliano Gabrielli | AlberT@SuperAlberT.it | Request | All | | Re: per entry "expand" in threaded view |
> > ok, i've downgraded my request then ...
> >
> > it will be still useful to have the possibility of expland selectively a single thread :-)
>
> That you can do by clicking on the thread and look at the thread at the top of the page (;-))
>
> That's exactly the same number of clicks as you would need to expand a thread (:-)))
LOL ..this way I can't see the list of other threads .. so il my goal is to inspect the thread
looking for something I have to:
- open the 3d
- return to 3d list
- open another 3d ..
[loop]
my wish would be to reduce it to
- open the 3d
- open another 3d ..
[loop]
of course I'm thinking to a big number of entries in a short number of 3ds .. making ugly to
simply expand everything .. :-) |
1127
|
Mon May 2 16:01:13 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | All | | Re: per entry "expand" in threaded view |
> LOL ..this way I can't see the list of other threads .. so il my goal is to inspect the thread
> looking for something I have to:
> - open the 3d
> - return to 3d list
> - open another 3d ..
> [loop]
>
> my wish would be to reduce it to
> - open the 3d
> - open another 3d ..
> [loop]
Well, I have the browser's back button on one of my mouse buttons, so "- return to 3d list" is one
mouse click. My policy is: If I can save someone two or more mouse clicks for am operation, I will
implement it. If it's less, it's not worth investing some hours of programming just to save 0.5s
each tim (;-).
Ok ok, I'll put it on the wish list. Just in case I'm running out of work. :-) |
1130
|
Sat May 7 17:51:22 2005 |
| damon nettles | nettles@phgrav.phys.lsu.edu | Question | All | | post box question |
is there any way to get a larger text box to type in when making a new post?
the default box is rather small and you have to scroll up and down when
making a new post or editing an existing one.
once the post is submitted, the display goes to a larger box, but the text
only takes up the left side of the page. seems the only way to get it to go
all the way to the right is to make everything html and submit it that way.
can the normal text look like the html does without submitting it as html? |
1131
|
Mon May 9 11:30:07 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | | Re: post box question |
> is there any way to get a larger text box to type in when making a new post?
> the default box is rather small and you have to scroll up and down when
> making a new post or editing an existing one.
Message width = <number of characters>
Message height = <number of lines>
> can the normal text look like the html does without submitting it as html?
No. |
1148
|
Thu May 12 18:32:18 2005 |
| damon nettles | nettles@phgrav.phys.lsu.edu | Question | All | | Re: post box question |
> > is there any way to get a larger text box to type in when making a new post?
> > the default box is rather small and you have to scroll up and down when
> > making a new post or editing an existing one.
>
> Message width = <number of characters>
> Message height = <number of lines>
>
> > can the normal text look like the html does without submitting it as html?
>
> No.
thanks stefan. it looks like it was right in front of my face the whole time (on
the elogd.cfg syntax page). but, somehow i missed it. |
1149
|
Tue May 17 21:38:36 2005 |
| Steve Jones | steve.jones@freescale.com | Bug report | All | 2.5.9 | Logbook locking issue |
Stefan, any ideas on this problem?
Quote: | Our eLog is set to create logbook entry locks and after 30minutes prevent one from re-editing an entry, thus forcing a REPLY to be created.
SCENARIO: When an *attempt* is made to edit a logbook after the 30minute timer, one gets the message that EDITING is prevented and to use the browser "Back" button.
PROBLEM: The display now shows that particular entry to be locked, even though the attempt to edit was blocked. It appears that the lock flag is set prior to the "Edit" attempt being blocked and thus the lock flag is never "unset". |
|
1165
|
Wed Jun 1 16:14:22 2005 |
| Steve Jones | steve.jones@freescale.com | Bug report | All | 2.5.9 | Re: Logbook locking issue |
Steve Jones wrote: | Stefan, any ideas on this problem?
Quote: | Our eLog is set to create logbook entry locks and after 30minutes prevent one from re-editing an entry, thus forcing a REPLY to be created.
SCENARIO: When an *attempt* is made to edit a logbook after the 30minute timer, one gets the message that EDITING is prevented and to use the browser "Back" button.
PROBLEM: The display now shows that particular entry to be locked, even though the attempt to edit was blocked. It appears that the lock flag is set prior to the "Edit" attempt being blocked and thus the lock flag is never "unset". |
|
Hmmm, I don't seem to be seeing any responses - is email being generated? |