Hi,

An update concerning problem 2

The problem occurs when I change the signature of one or more functions in an imported module.

If there are too many functioncalls in my main program triggering an error because of this change in signature of the called function than the errorstatusmessages in the editor window get out of sync.

An work around is to split the main program in a small first file and a large second file.

After debugging the first file I copy an amount of new code from the second file into the debugged first file and start debugging the new copied code.

This is repeated until all code is copied into the first part and the second part is empty.

Resumé: It is not the size of the program that triggers the sync-problem with the errorstatusmessage but the amount of errors, which in a large program is higher than in a small program.

Hope this helps solving the problem.

Regards,

Rob Stapper

Van: Rob Stapper [mailto:r.stapper@lijbrandt.nl] Verzonden: zaterdag 26 oktober 2013 13:45 Aan: 'basex-talk@mailman.uni-konstanz.de' Onderwerp: strange behaviour of the BaseXgui-editor

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