Hi,
I encountered a few (3) problems with the BasexGui-editor.
I use the 7.8 beta release but the issue's also occur in previous versions.
Problem 1:
this is a minor problem but maybe related to problem 2 which is ( for me) a major problem:
If I open two ( small) packages of which one has no errors and one has errors then the errorstatus-message at the bottom of the editor doesn't synchronize correctly when switching files.
If I switch from the incorrect packagefile to the correct packagefile the errormessage doesn't refresh to 'ok' until I edit this file.
Even after closing an activated incorrect packagefile the errormessage stays active. Clicking on the message even reopens the incorrect packagefile.
Switching the focus from the correct packagefile to the incorrect packagefile however, doesn't show this behavior. In that case the errorstatus-message changes to the appropriate errormessage of the incorrect file.
Problem 2:
which is a major problem when working with big files ( 80 kB)
I found that when editing a large(r) packagefile the Basexgui-editor doesn't recognize errors that occur after a certain point in the file.
If errors occur after this point the errorstatus-message shows 'ok' but I know that the file contains errors and if I try to install the file as a package I get an window with the message below.
If the error occurs before that certain point then I get an correct errormessage. However if I delete the code which contains the error the error-message remains.
Clicking on the message brings the cursor to the point where the deleted code with the error used to be, even after saving and closing the file.
Errormessage
============================================================================ ==============================================
Improper use? Potential bug? Your feedback is welcome:
Contact: basex-talk@mailman.uni-konstanz.de
Version: BaseX 7.8 beta
Java: Oracle Corporation, 1.7.0_45
OS: Windows Vista, x86
Stack Trace:
java.lang.NullPointerException
at org.basex.query.func.StaticFuncs.check(StaticFuncs.java:121)
at org.basex.query.QueryParser.finish(QueryParser.java:312)
at org.basex.query.QueryParser.parseLibrary(QueryParser.java:253)
at org.basex.query.QueryContext.parseLibrary(QueryContext.java:197)
at org.basex.query.util.pkg.RepoManager.installXQ(RepoManager.java:230)
at org.basex.query.util.pkg.RepoManager.install(RepoManager.java:70)
at org.basex.core.cmd.RepoInstall.run(RepoInstall.java:37)
at org.basex.core.Command.run(Command.java:344)
at org.basex.core.Command.exec(Command.java:320)
at org.basex.core.Command.execute(Command.java:77)
at org.basex.core.Command.execute(Command.java:89)
at org.basex.gui.dialog.DialogProgress$1.run(DialogProgress.java:178)
============================================================================ ==============================================
Being a responsible Basex-user I does what it says and give you some feedback J
Problem 3:
This is an old issue that I addressed e few months ago but which you could not reproduce.
I found a new clue which might help you solving this issue.
The issue was when working in fullscreen mode (F11) in the BasexGUI and then saving a file with 'save as .'
The save-messagebox gets the focus but disappears behind fullscreen basexgui-window.
This has something to do with using a dual monitorsystem.
On a single monitor system it works ok: The save-box is placed on top of the fullscreen Basexgui-window and gets the focus.
On a dualmonitorsystem the save-box is placed behind the fullscreen Basexgui-window and gets the focus.
I hope this insight helps you tackle this minor issue.
Well, that's all folk. I hope you can solve the editor-problem soon because I have a really hard time debugging my (large(r)) programs.
Regards,
Rob Stapper
Problem 1: [...] If I open two ( small) packages of which one has no errors and one has errors then the errorstatus-message at the bottom of the editor doesn’t synchronize correctly when switching files.
Just to be sure: what do you mean with packages? do you refer to XQuery library modules?
I guess there are various reasons for the surprising behavior. The most prominent one is that, when a query is run, an error may occur in another module than the one that is currently displayed in the edit. By clicking on the error message, or by typing Ctrl+., you can jump to the buggy file, line and column. If we parsed the file every time another tab is chosen, this error message disappears. The rational behind this was that buggy code always needs to be fixed anyway, but I know feelings about this can be mixed.
Problem 2: [...]
I read your second mail, but it’s still difficult to figure out what’s going on. Maybe you could manage to provide us with some minimized example code?
Improper use? Potential bug? Your feedback is welcome: […] Being a responsible Basex-user I does what it says and give you some feedback J
Thanks ;) Looks like a clear bug. Let’s see if we can guess what was the reason for that. I’ve added an issue to our bug tracker [1].
Problem 3: […] This has something to do with using a dual monitorsystem.
Well, this is difficult for me to reproduce, as I don’t work with multiple monitors. Some volunteers out there? I’m not even sure if we can fix this is at all, as this might be a Java/Swing issue. The obvious workaround is to avoid fullscreen mode (it may be removed anyway).
Christian
Hi Rob,
I managed to fix the bug, and I’ve uploaded a new stable snapshot [1].
Thanks, Christian
[1] http://files.basex.org/releases/latest/ ___________________________
2013/10/26 Christian Grün christian.gruen@gmail.com:
Improper use? Potential bug? Your feedback is welcome: [...] Contact: basex-talk@mailman.uni-konstanz.de
Can you also provide an example query that triggered this exception?
Hi Rob,
we have just reworked the way exceptions are handled in the GUI editor. As a positive side effect, some of the problems you encountered with the error status messages should now be resolved. Your feedback on the latest stable snapshot is welcome [1].
Best, Christian
[1] http://files.basex.org/releases/latest ___________________________
On Sat, Oct 26, 2013 at 1:44 PM, Rob Stapper r.stapper@lijbrandt.nl wrote:
Hi,
I encountered a few (3) problems with the BasexGui-editor.
I use the 7.8 beta release but the issue’s also occur in previous versions.
Problem 1:
this is a minor problem but maybe related to problem 2 which is ( for me) a major problem:
If I open two ( small) packages of which one has no errors and one has errors then the errorstatus-message at the bottom of the editor doesn’t synchronize correctly when switching files.
If I switch from the incorrect packagefile to the correct packagefile the errormessage doesn’t refresh to ‘ok’ until I edit this file.
Even after closing an activated incorrect packagefile the errormessage stays active. Clicking on the message even reopens the incorrect packagefile.
Switching the focus from the correct packagefile to the incorrect packagefile however, doesn’t show this behavior. In that case the errorstatus-message changes to the appropriate errormessage of the incorrect file.
Problem 2:
which is a major problem when working with big files ( 80 kB)
I found that when editing a large(r) packagefile the Basexgui-editor doesn’t recognize errors that occur after a certain point in the file.
If errors occur after this point the errorstatus-message shows ‘ok’ but I know that the file contains errors and if I try to install the file as a package I get an window with the message below.
If the error occurs before that certain point then I get an correct errormessage. However if I delete the code which contains the error the error-message remains.
Clicking on the message brings the cursor to the point where the deleted code with the error used to be, even after saving and closing the file.
Errormessage
==========================================================================================================================
Improper use? Potential bug? Your feedback is welcome:
Contact: basex-talk@mailman.uni-konstanz.de
Version: BaseX 7.8 beta
Java: Oracle Corporation, 1.7.0_45
OS: Windows Vista, x86
Stack Trace:
java.lang.NullPointerException
atorg.basex.query.func.StaticFuncs.check(StaticFuncs.java:121)
at org.basex.query.QueryParser.finish(QueryParser.java:312) atorg.basex.query.QueryParser.parseLibrary(QueryParser.java:253)
atorg.basex.query.QueryContext.parseLibrary(QueryContext.java:197)
atorg.basex.query.util.pkg.RepoManager.installXQ(RepoManager.java:230)
atorg.basex.query.util.pkg.RepoManager.install(RepoManager.java:70)
at org.basex.core.cmd.RepoInstall.run(RepoInstall.java:37) at org.basex.core.Command.run(Command.java:344) at org.basex.core.Command.exec(Command.java:320) at org.basex.core.Command.execute(Command.java:77) at org.basex.core.Command.execute(Command.java:89) atorg.basex.gui.dialog.DialogProgress$1.run(DialogProgress.java:178)
==========================================================================================================================
Being a responsible Basex-user I does what it says and give you some feedback J
Problem 3:
This is an old issue that I addressed e few months ago but which you could not reproduce.
I found a new clue which might help you solving this issue.
The issue was when working in fullscreen mode (F11) in the BasexGUI and then saving a file with ‘save as …’
The save-messagebox gets the focus but disappears behind fullscreen basexgui-window.
This has something to do with using a dual monitorsystem.
On a single monitor system it works ok: The save-box is placed on top of the fullscreen Basexgui-window and gets the focus.
On a dualmonitorsystem the save-box is placed behind the fullscreen Basexgui-window and gets the focus.
I hope this insight helps you tackle this minor issue.
Well, that’s all folk. I hope you can solve the editor-problem soon because I have a really hard time debugging my (large(r)) programs.
Regards,
Rob Stapper
BaseX-Talk mailing list BaseX-Talk@mailman.uni-konstanz.de https://mailman.uni-konstanz.de/mailman/listinfo/basex-talk
basex-talk@mailman.uni-konstanz.de
-
Christian Grün -
Rob Stapper