Re: Auto save?, posted by Stefan Ritt on Mon Jul 1 09:59:18 2013
|
| Andreas Luedeke wrote: |
|
| Daniel Roldan wrote: |
|
Hi,
One question, is possible activate auto-save while write a new "ticket"?
Thanks very much.
|
It is not clear to me, what you mean by "activate auto-save".
Do you mean that you want to have the typed in data in your forms temporarily saved, to be restored e.g. after a crash of the browser?
This functionality has to be provided by the browser. I use the add-on "Lazarus: form recovery" for firefox, that works fine for me.
⇄
Detect language » English
Regards Andreas
|
Great that you pointed out this possibility. I saw that Lazarus Form Recovery is even available for Google Chrome and it works fine. It however works only for the "EL Code" and "plain" encodings. In the "HTML" edit box it does not work (probably some collision with the FCKEditor). If anybody has an idea about this, please post it.
/Stefan |
|
Re: update to ckeditor (formerly: Auto save?), posted by Andreas Luedeke on Mon Jul 1 13:30:28 2013
|
| Stefan Ritt wrote: |
|
| Andreas Luedeke wrote: |
|
| Daniel Roldan wrote: |
|
Hi,
One question, is possible activate auto-save while write a new "ticket"?
Thanks very much.
|
It is not clear to me, what you mean by "activate auto-save".
Do you mean that you want to have the typed in data in your forms temporarily saved, to be restored e.g. after a crash of the browser?
This functionality has to be provided by the browser. I use the add-on "Lazarus: form recovery" for firefox, that works fine for me.
⇄
Detect language » English
Regards Andreas
|
Great that you pointed out this possibility. I saw that Lazarus Form Recovery is even available for Google Chrome and it works fine. It however works only for the "EL Code" and "plain" encodings. In the "HTML" edit box it does not work (probably some collision with the FCKEditor). If anybody has an idea about this, please post it.
/Stefan
|
Hi Stefan,
that reminds me of something: you've wanted to upgrade from the obsolete FCKEditor to the successor CKEditor. That would allow to use the cool editor for math formulas: http://www.fmath.info/plugins/CKEditor/demo.jsp
⇄
Detect language » English
http://www.fmath.info/plugins/CKEditor/demo.jsp
Cheers, Andreas |
Navigation previous and next button don't work, posted by Hung Dao on Thu Oct 10 21:03:09 2013
|
| I am having a problem with the navigation buttons when clicking previous or next button. It does not do anything. Has anyone had this same problem? I am also using IE 10. But it seems also having a same problem on Firefox. |
|
Re: Navigation previous and next button don't work, posted by Stefan Ritt on Fri Oct 11 09:44:42 2013
|
| Hung Dao wrote: |
| I am having a problem with the navigation buttons when clicking previous or next button. It does not do anything. Has anyone had this same problem? I am also using IE 10. But it seems also having a same problem on Firefox. |
Have you tried on this forum? |
|
Re: Navigation previous and next button don't work, posted by Mark Campbell on Fri Oct 11 10:18:04 2013
|
| Stefan Ritt wrote: |
|
| Hung Dao wrote: |
| I am having a problem with the navigation buttons when clicking previous or next button. It does not do anything. Has anyone had this same problem? I am also using IE 10. But it seems also having a same problem on Firefox. |
Have you tried on this forum?
|
The navigation buttons work for me but Ctrl-PgUp and Ctrl-PgDn does not in IE8 or Chrome.
However buttons and Ctrl-PgUp and Ctrl-PgDn both work in FireFox, so seems to be browser specific, I noted that in Chrome Ctrl-PgUp and Ctrl-PgDn moves through your open Tabs. |
|
Re: Navigation previous and next button don't work, posted by Stefan Ritt on Fri Oct 11 10:21:52 2013
|
| Mark Campbell wrote: |
|
| Stefan Ritt wrote: |
|
| Hung Dao wrote: |
| I am having a problem with the navigation buttons when clicking previous or next button. It does not do anything. Has anyone had this same problem? I am also using IE 10. But it seems also having a same problem on Firefox. |
Have you tried on this forum?
|
The navigation buttons work for me but Ctrl-PgUp and Ctrl-PgDn does not in IE8 or Chrome.
However buttons and Ctrl-PgUp and Ctrl-PgDn both work in FireFox, so seems to be browser specific, I noted that in Chrome Ctrl-PgUp and Ctrl-PgDn moves through your open Tabs.
|
I confirm that IE8 and Chrome "eat" the Ctrl-PgUp/Dn keys, so they are not passed to ELOG, and there is nothing I can do about. |
|
Re: Navigation previous and next button don't work, posted by David Pilgram on Fri Oct 11 11:19:00 2013
|
| Stefan Ritt wrote: |
|
| Mark Campbell wrote: |
|
| Stefan Ritt wrote: |
|
| Hung Dao wrote: |
| I am having a problem with the navigation buttons when clicking previous or next button. It does not do anything. Has anyone had this same problem? I am also using IE 10. But it seems also having a same problem on Firefox. |
Have you tried on this forum?
|
The navigation buttons work for me but Ctrl-PgUp and Ctrl-PgDn does not in IE8 or Chrome.
However buttons and Ctrl-PgUp and Ctrl-PgDn both work in FireFox, so seems to be browser specific, I noted that in Chrome Ctrl-PgUp and Ctrl-PgDn moves through your open Tabs.
|
I confirm that IE8 and Chrome "eat" the Ctrl-PgUp/Dn keys, so they are not passed to ELOG, and there is nothing I can do about.
|
On this linux box, using Firefox 12, if tabs are in use, Ctrl-Pgup/Ctrl-Pgdn goes throught the tabs. If you force tabs off, then it goes through the entries.
Bavigation buttons work fine. |
|
Re: Navigation previous and next button don't work, posted by Hung Dao on Fri Oct 11 15:59:39 2013
|
| Stefan Ritt wrote: |
| Hung Dao wrote: |
| I am having a problem with the navigation buttons when clicking previous or next button. It does not do anything. Has anyone had this same problem? I am also using IE 10. But it seems also having a same problem on Firefox. |
Have you tried on this forum? |
I have tried this forum, it worked fine. So, it should not be a browser. The only different I have logbook that I have been working on ELOG v2.6.5 and I have installed a new version v2.9.2. I just wonder any different data format (2.6.5 vs. 2.9.2) could have caused a problem.
|