1.9.9
To be honest my skill at keeping track of things is very poor.
So all I can say is that not much has changes.
An option has been added to MISC tab to choose using Tools.prefs and Templates.prefs from the shared preferences while an editor is running its own isolated PureBasic.prefs and History.db in its own folder.
Code organizing and what nots also done I guess.
Now I think I have reached the end of this journey.
1.11
Sorry, 1.10 had a bug with the recent file, recent projects cleaner.
Swapped out how it is named so PureBasic_Portable_x86.exe and PureBasic_Portable.exe are now how they each are compiled. This also means I had to tweak the Change Theme tool and is pre-installed in the tools folder.
Now I want to move on to a new project. What ever that will be I don't know.
Alright, alright, I know I keep saying I am going to stop working on this.
But ideas haunt my idle time and before you know it I am playing around with the code of this thing.
1.18
Maybe the last one. but that hasn't been the track record.
I had been experiencing strange behavior with the editor when launched, not exactly being fully focused?
This caused oddities with gaining and maintaining focus on controls in the preferences dialog, tools dialog, find dialog. basically anything.
1.19 attempts to correct this behavior with a new togglable option that seems to fix the issue, despite the fact I may be way off base about what I have been experiencing.
1.23
Added some mediocre detection to prevent attempts to install a version that already exists.
it can't tell the difference now between the 5.73 x86 installer and the 5.73 x64 installer (same name after striping the random download hash (xxxxx))
So it will warn you that it may already exist if one of them has already been installed, and ask you if you want to try the install anyways.
If it fails it is because it can't rename the extracted folder named {app} to the actual installed version name because it already exists. It will then delete the extracted folder named {app}
It can determine between the PureBasic 6 releases though. and brings up same warning if it finds an install that matches.
It continues without warning to the TAC and installation if it can be certain there is no match.
This all relies on the install_script.iss that is placed inside each PureBasic directory that is installed.
If the install_script.iss is missing it will go straight to the TAC and installer.
1.26 is nothing special.
some code cleaning and also added a warning at start if it detects a space in its path.
Protects you from wasting your time installing a PureBasic, only for {app} to fail its rename because of said space(s) in the path. So it will then give you an error that you can not install while there is a space in its path. Not sure what else is effected by spaces. not thoroughly tested this yet.
I will work on trying to do relative paths as much as possible with an upcoming version to see if I can bullet proof that problem. Not sure if it is possible yet.
Found the errors of my ways. at install the area that generates the new name Was trying to swap out space for underscores along the entire path, failing when trying to rename folders above its home directory because running application (itself)
Fixing this took making it generate its new name first, then attach it to the home path in the renamefile() command.
1.29
Nothing much noticeable to the end user other than the About tab.
Under the hood: a bit of code cleaning or mucking (Subjective)
Made some compilerif directives that are necessary for compilation pre-PB6 if there is ever a need.
info in the about tab uses PureBasic 6 only constants, so I had to create directives for backwards compellability.
What ever else I cant remember.
I guess if I ever post another version I will make sure it has some sort of end user value. However I am having trouble thinking of more tools that would be useful Pre-lauch.