@touwys, can you to try the new Windows installer(s)?

@touwys, can you to try the new Windows installer(s)?

Installed via the MSI to the default directory, C:\Users\*\AppData\Local

The installation was problem-free, and the app also started without any apparent issues.

@touwys, can you to try the new Windows installer(s)?

Installed via the MSI to the default directory, C:\Users\*\AppData\Local

I was a bit surprised by that as well, seems to be an individual installation rather then a shared installation.
Need to check if I can customize that.

The installation was problem-free, and the app also started without any apparent issues.

Version is missing in application window title:

Also the application is listed as "listfix" instead of "lisFix()".

Is not once logged, sufficient?

In principal that is sufficient. I think this one is introduced in #164, which is kind of the groundwork for this PR, therefor I will address in this PR. I remember you have reported it before, but I think that was based on a screenshot I provided, running it in dev environment, but I could be wrong. Doesn't matter.

@Borewit

"Save Playlist Error"

I am logging this build-error here, instead "Issues":

Unfortunately, I did not keep track of the steps that have led up to this error, but I did take the screenshot below. Does it help any?

Playlist Saving Error _ Screenshot 20230425

•••••••

Can you try this this PR again @touwys?

• I think I resolved the "Save Playlist Error" via Fix uncommon root path exception #170, which now included here as well.
• Name corrected
• windows update GUI added, which correlate updates (best to de-install previous version)
• Fixed version number

Build: Windows

listFix_2.7.0-11:

I think I resolved the "Save Playlist Error" via Fix uncommon root exception #170, which now included here as well. ❔

I could not reconstruct this error, confidently. Because, originally, it was induced purely by accident. Were you able to reconstruct the exact steps from the error report submitted?

Name corrected. ✔️

windows update GUI added, which correlate updates (best to de-install previous version) ✔️

No issues here. It lands on this page proper: Releases · Borewit/listFix

Fixed version number ✔️

Below there are screenshots, some annotated, that graphically display some of the immediate results. I propose that the start-up splash screen gets modified to something similar to the one shown:

•
Default install directory:

•
Current splash screen:

•
Proposed splash screen:

•
Playlist tab not refreshing, invariably.

•

@Borewit :
In the case of listFix(), how are the graphical elements incorporated into the software? Are these elements — for example the start-up splash screen — designed in another programme, ready to be imported for assimilation in the listFix() development package?

@Borewit : In the case of listFix(), how are the graphical elements incorporated into the software? Are these elements — for example the start-up splash screen — designed in another programme, ready to be imported for assimilation in the listFix() development package?

I reversed engineered the original splash screen to SVG which can be found here.

One of the apps able to edit SVG is inkscape, or a text editor is enough to change a position.

Note that the fourth digit group (.11) is the commit distance from the last release, that one will not be present the real release.

I could not reconstruct this error, confidently. Because, originally, it was induced purely by accident. Were you able to reconstruct the exact steps from the error report submitted?

No, but based on the error I think this is caused when the paylist is one drive, and at least one track on another drive. Then enable the relative path, and that is probably the way to reproduce it.

Playlist tab not refreshing, invariably.

I think the Playlist tab not introduced in this PR, so I guess best to create a new issue for that.

I reversed engineered the original splash screen to SVG which can be found here.

What about any of the other GUI elements contained in the app — are there elements other than the splash-screen that may need an update/redesign from time-to-time? If here are, I would like to offer to help you with that, as far as I am able to. Also, is it imperative that all such images be presented in the SVG-format?

Note that the fourth digit group (.11) is the commit distance from the last release, that one will not be present the real release.

Yes, I am aware of that, but I submit that the centralised version number is more versatile and neater.

Also, is it imperative that all such images be presented in the SVG-format?

SVG is the best foundation to store graphics. As it is commonly used, vector based (scale-able without loss of quality), it is code (text) (works well with repo and it allows to manipulate text). For some type of graphics is less suitable.

I did some experiments with regenerating buttons, but I though the result of that was fairly disappointing. It looks like the Java Swing GUI as good in rendering graphics as browsers are nowadays. Buttons looked very pixelated. Maybe that gets better switching to JavaFx.