WinFBE Editor and FreeBASIC Compiler (All-in-One Package) (V3.2.0 May 29, 2025)

[St_W]

And the same problem is then select compiler. I joined x86 and x64 compilers into one directory, so I couldn't give both the same name. Thus I named x64 compiler as fbc_x64.exe. And it would be great if you allow to select any *.exe instead fbc.exe

I sometimes do the same (merging x86 and x64 FB directories) but beginners probably wouldn't do this. And as a non-beginner you can select "All files (*.*)" in the dialog while beginners can easiliy find fbc.exe and will not select a wrong executable. So IMHO the decision is fine. Maybe add a "Executables (*.exe)" filter instead of replacing the fbc.exe filter.

[PaulSquires]

Okay, I updated all of the filters as well as the select compiler (I added Executable *.exe). You can download the new exe's directly from GitHub. You will also need to download the language files. I have not done a separate release just for this small change.

[PaulSquires]

Version 1.4.9 (August 31, 2017)
- Changed: If "Allow multiple instances" is unchecked, then subsequent file opens will open in the current active editor instance.
- Changed: Filters for "Save As", "Save Declares File", "Open', "Insert File" and "Select Compiler".
- Fixed: Explorer Treeview filenames immediately resorted when filename changed (new file or save as).

https://github.com/PaulSquires/WinFBE/releases

[MrSwiss]

Hi Paul,

cool, just tried the last version (short test only).

I've noticed a slight problem, concerning the background (color) setting ...
I personally prefer a dark bg (aka: black), e.g. "MrHoundcat" theme, on FBEdit.

Switching to: Window = "black", gives a very ugly 'picture' ... (except every single
bg color is reset (which seems to be 'unfeasible', to stay polite).

Proposed solution:
on all bg adjustments, offer "transparent" as additional "option" (default setting).
This enables a different bg-setting, without any additional "work" for the user.

Alternative:
Theme support (maybe)??

[PaulSquires]

Hi MrSwiss, good points. I guess I haven't looked at the coloring options for quite some time as (like most people) once you have your colors set you don't really think about it again. :-)

I will see what I can do to re-work the way that colors are setup in order to make it easier and less intrusive for the user when colors are changed.

I like the idea of themes.

[PaulSquires]

...I am making the changes with color backgrounds and Themes. Should have it coded and ready for public consumption this weekend.

[MrSwiss]

Great news, however, take your time, its not top notch priority ...

[PaulSquires]

Redesigning the color system was a good idea. Here is a screenshot of WinFBE with the new theme capability. Behind the dialog you will see the theme in action as it colorizes the code using the "Visual Studio Code (Dark)" theme. I am debating if I want to try to extend the theme to also color the Explorer panel.

I have also added environment options to show/hide the main window toolbar and statusbar.

All changes will be in the next upload.

[MrSwiss]

Hi Paul,

you wrote:
> I am debating if I want to try to extend the theme to also color the Explorer panel.

I for one thinking that, extending the theme, to cover "all" the inner windows, is a good idea ...
(similar to the themes in FBEdit, currently) Thanks for your efforts to really get WinFBE rolling.

It might seem trivial at first sight, but I think, feeling comfortable with the tool of choice, is very
important for every day use (and therefore, a wide acceptance, since people have different view-
points, likes or dislikes etc.).

[PaulSquires]

I agree that the inner windows should be themed. I reprogrammed the Explorer and recent files/projects windows to use user specified colors but the results are not acceptable. As you know, in order to use non-standard Windows system colors for Treeviews you need to use CustomDraw methods. That worked with no problem but there are still elements of the control that you can not recolor such as as the expand/collapse boxes (I would have to implement my own icons) and the scrollbars. The scrollbars are the biggest problem because they detract hugely from the aesthetics when they remain as the standard Windows grayish colors. There is no easy way to intercept scrollbar paint messages in order to change them. For the next release I will not theme the inner windows but I am working on a much better solution that I will show in the next week or two.

[PaulSquires]

Version 1.5.0 (September 3, 2017)
- Added: Theme support. Create user defined color themes.
- Added: Default Theme and Visual Studio Code (Dark) theme.
- Added: "User selected" option when choosing colors allows user to select any color rather than just the predefined ones.
- Added: Environment option to show/hide main window Toolbar and Statusbar.
- Fixed: Screen artifacts on code window when Explorer resized.

https://github.com/PaulSquires/WinFBE/releases

(Note: You will lose any color settings that you have defined in previous versions of WinFBE. WinFBE now uses a theme system so you will have to create your own theme and define and save your custom color settings there).

[PaulSquires]

Version 1.5.1 (September 3, 2017)
- Fixed: Accidentally included unfinished visual designer code in v1.5.0 release.

https://github.com/PaulSquires/WinFBE/releases

[sancho2]

How about user-submitted themes?
Are you saving themes in a separate file or is it all in one config?
If it is a separate file then a person could share their theme with others.

[PaulSquires]

How about user-submitted themes?
Are you saving themes in a separate file or is it all in one config?
If it is a separate file then a person could share their theme with others.

Themes are stored in the WinFBE.ini file.
Instead of changing the current approach to that of using separate files, I will add a button to import a theme from an external file.

[Jonge]

Any chance of getting Bold and Italic settings on fonts?