BaseX 13.0 doesn't store anything in the .basexgui file
Hi all,
First off, thanks for BaseX 13.0! When testing the GUI (Windows 11, via the bin\basexgui.bat script), I noticed a couple of quirks:
* the editor doesn't store opened files * the editor doesn't remember changes to paths set in "Database" > "Preferences"
In my previous BaseX instance, I found those were written out in the .basexgui file. While this file is present in my BaseX 13.0 installation, it remains empty, so nothing seems to be stored.
Am I overlooking something in the upgrade process?
Best,
Ron
Hi Ron,
Thanks for the observation. The mechanism in the GUI has not changed, but our installer has:
1. Can you confirm that your installation of BaseX has gone into the global 64-bit program directory (usually c:\Program Files\)? 2. If so, I would be interested to hear whether the issue persists with the latest stable snapshot [1].
BaseX 13.1 is planned for next week or the week after.
All the best, Christian
Quoted text · ron.vdbranden · 15 lines
ron.vdbranden--- via BaseX-Talk <basex-talk at mailman.uni-konstanz.de> schrieb am Montag, 9. November 2026 um 12:19: > Hi all, > > First off, thanks for BaseX 13.0! When testing the GUI (Windows 11, via the bin\basexgui.bat script), I noticed a couple of quirks: > > - the editor doesn't store opened files > - the editor doesn't remember changes to paths set in "Database" > "Preferences" > > In my previous BaseX instance, I found those were written out in the .basexgui file. While this file is present in my BaseX 13.0 installation, it remains empty, so nothing seems to be stored. > > Am I overlooking something in the upgrade process? > > Best, > > Ron
Hi Christian,
Many thanks for your quick response and fix!
I was suspecting the new 64-bit install location under "c:\Program Files\" could be related but forgot to mention that.
Tested with the latest snapshot, I can confirm the issue has been fixed.
Best,
Ron
Quoted text · Christian Grün · 43 lines
On 09/11/2026 12:56, Christian Grün wrote: > Hi Ron, > > Thanks for the observation. The mechanism in the GUI has not changed, > but our installer has: > > 1. Can you confirm that your installation of BaseX has gone into the > global 64-bit program directory (usually c:\Program Files\)? > 2. If so, I would be interested to hear whether the issue persists > with the latest stable snapshot [1]. > > BaseX 13.1 is planned for next week or the week after. > > All the best, > Christian > > [1] https://files.basex.org/releases/latest/ > ____________________________________ > > ron.vdbranden--- via BaseX-Talk <basex-talk at mailman.uni-konstanz.de> > schrieb am Montag, 9. November 2026 um 12:19: >> >> Hi all, >> >> First off, thanks for BaseX 13.0! When testing the GUI (Windows 11, >> via the bin\basexgui.bat script), I noticed a couple of quirks: >> >> * the editor doesn't store opened files >> * the editor doesn't remember changes to paths set in "Database" > >> "Preferences" >> >> In my previous BaseX instance, I found those were written out in the >> .basexgui file. While this file is present in my BaseX 13.0 >> installation, it remains empty, so nothing seems to be stored. >> >> Am I overlooking something in the upgrade process? >> >> Best, >> >> Ron >> >> >
Written for BaseX 12.4. BaseX may have changed since: please check the current documentation.