Error on Mac OS: about litball

[rwst]

Thanks for reporting. The error looks like it couldn't write settings.json, which is written, on Linux, in the install directory, from which the app is run. I will have to find out how this is usually handled on Mac.

[Adafede]

I can confirm have it created in the directory locally when running gradle run

[rwst]

In this new release I use System.getProperties("user.dir") as path to the settings file:
https://github.com/rwst/LitBall/releases/tag/v2316
Could you please, when you have the occasion, try to install the Mac binary?

Your screenshot looks fine, except for the error, so I'm excited to hear about your results.

[Adafede]

Sorry, changed the path of the error but did not solve it :(

[rwst]

Thanks.
OK, somone pointed me to a library that handles system-specific directories and so I would ask you to try this;
https://github.com/rwst/LitBall/releases/tag/v2317

[Adafede]

Slowly getting there!

The initial bug is gone (👍🏼), but now the next generated file when creating a query is the issue...
see below (my query was named lotus)

[rwst]

What is your query directory setting? What if you set it to a new directory made by you?

…

On Tue, 26 Sep 2023, 18:34 Adriano Rutz, ***@***.***> wrote: Slowly getting there! The initial bug is gone (👍🏼), but now the next generated file when creating a query is the issue... see below [image: Screenshot 2023-09-26 at 18 32 51] <https://user-images.githubusercontent.com/44283913/270729967-565a3feb-e87a-4862-8760-0c4bf4642481.png> — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIX6VM72F34TUTEMLSQEWDX4L7ZDANCNFSM6AAAAAA5HIC4SA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Adafede]

I did let the default one (/Query-).

Changing it to nothing did not solve the issue.

I could not create new ones:

[rwst]

What I meant was create any, or even use an existing directory, and put that in the query path setting, not the prefix. The prefix is just to have a common prefix that is recognised by the app.

…

On Tue, 26 Sep 2023, 21:07 Adriano Rutz, ***@***.***> wrote: I did let the default one (/Query-). [image: Screenshot 2023-09-26 at 21 05 23] <https://user-images.githubusercontent.com/44283913/270768647-b8deca2b-1898-4af4-ae10-a61cae46d5b7.png> Changing it to nothing did not solve the issue. I could not create new ones: [image: Screenshot 2023-09-26 at 21 06 12] <https://user-images.githubusercontent.com/44283913/270768927-c7068f96-07a2-4137-99df-6faf5c5c7f1c.png> — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIX6VPPPYNU6FQQJSE75ZLX4MRU7ANCNFSM6AAAAAA5HIC4SA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Adafede]

after the above warning blocking the app, I could re-open it from the command line and it had mydir as default dir which then allowed me to perform the queries as with the local install:

[rwst]

Yeah, I think the only issue is the default setting, which should be rather the platform specific user dir.

…

On Tue, 26 Sep 2023, 21:16 Adriano Rutz, ***@***.***> wrote: after the above warning blocking the app, I could re-open it from the command line and it had mydir as default dir which then allowed me to perform the queries as with the local install: [image: Screenshot 2023-09-26 at 21 14 56] <https://user-images.githubusercontent.com/44283913/270771579-d566b16d-a9a1-43b4-af2f-caf790f0e917.png> — Reply to this email directly, view it on GitHub <#1 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAIX6VLKOQJW4EHWAYE4UP3X4MSXTANCNFSM6AAAAAA5HIC4SA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[rwst]

OK thanks again. I believe all read-only problems of new installations are fixed in ths release:
https://github.com/rwst/LitBall/releases/tag/v2318

Also, your editing of the query prefix setting uncovered a design problem, which I will address in a later release, probably by introducing Advanced Settings, and of course, more documentation.