WinFBE.ini - what to do?

[Bruce Huber]

Paul, since you are a crazy person who works very hard on WinFBE and updates it quite often...
- and since I am a crazy old man who likes his dark edit theme and they way he has everything set up in "his" WinFBE...
- and since there is no way for me to know if you have made a new/breaking change to the WinFBE.ini file in any of the 6 new versions you have created on any given day....

I have to save my .ini file - download the new WinFBE - and diff your and my .ini file to see if I need to add/change anything in mine.

And if I didn't step on my own tail and screw up forget to save off my .ini file occasionally, it wouldn't be a problem... but... stuff happens. [smile]

Is anyone else out there facing this extremely difficult first-world-problem themselves - and has anyone figured out a simple, automatic method of handling this?

Thanks!
Bruce

[SeaVipe]

Hi Bruce, for each new version of WinFBE, I rename the old version to C:\WinFBE_Suite.x.x.x and then upzip the latest version directly to C:\. Then I copy WinFBE.ini (so I keep my dark theme), FreeBasic_Keywords.txt (I've added a few words that I like coloured) and user_snippets.ini from the old version to the new WinFBE_Suite\Settings folder. I check out WinFBE.ini to see if anything in there has changed that I need to know about. (This may not be the recommended way of doing things but it works for me.)

[Paul Squires]

Ah, yes, I can see how this would be a problem when updating. Usually the WinFBE.ini configuration file does not change but I can see the user_snippets.ini being a bigger problem if the new install overwrote a person's large collection snippets. Not sure how to handle this yet.

[SeaVipe]

Maybe a user defined location for snippets and themes?

[Paul Squires]

I have implemented the following solution:

The following files will no longer be included in the WinFBE_Suite downloads:
(1) WinFBE.ini
(2) user_snippets.ini
(3) freebasic_keywords.txt

Therefore, you should be able to simply unzip a WinFBE_Suite rar archive directly over an existing installation without the risk of losing any of your user defined editor configurations (eg. colors, builds, etc), or overwriting any user defined snippets or new keywords that you have entered.

The WinFBE.ini will automatically be created if it does not exist.
The user_snippets.ini will be created via copying data from a supplied user_snippets_default.ini file.
The freebasic_keywords.txt will be created via copying data from a supplied freebasic_keywords_default.txt file.

This should make dealing with updates a little easier.

[Bruce Huber]

First, the question...

So, if you implement changes/additions to WinFBE.ini that would cause problems if we were to continue just using our existing version, or if you add new keywords... we will simply need to check a "readme" first... (or have you gone crazy and built in a merge or something)? [smile]

And, second....

THANKS PAUL!!!
Bruce

[Paul Squires]

You're very welcome :-)

Should the WinFBE.ini ever change then I'll simply build code in the editor to add or delete the sections from an existing WinFBE.ini. Checking the readme is always good practice however probably not so much these days as the editor has matured and stabilized...but in the early days things would change widely between releases.