WinFBE Editor and FreeBASIC Compiler (All-in-One Package) (V2.1.8 November 19, 2020)

[fxm]

Declare all procedures (including member procedures) as private (only internal linkage) is very simple if compiling in -lang deprecated or fblite or qb, because we have just to add 'Option Private' at the top of the main file (before any code and file inclusions).
Otherwise (-lang fb for example), 'Option Private' is not allowed and so we must specify 'Private' at the level of each procedure body (including for the modules to include). Therefore, these modules can no longer be used as external modules as well.

[fxm]

Version 1.3.9 (July 25, 2017)
- Added: Option (Environment Options :: Compiler Setup) to run compiled programs from a spawned command window. Useful for catching runtime errors.

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


Not in this release but coming soon:
- enhancing the logic for "Run Executable".
- implement option prompt user for confirmation with messagebox when closing the editor.
- implement a Build Options dialog in order to create user defined compile/build options. Release, Debug, 32bit, 64bit, etc....

A "Quick Run" command, like many other IDEs (compilation + execution, using only temporary files), can be useful because it allows you to test a temporary code without saving it (neither modify existing source files of user).

[PaulSquires]

A "Quick Run" command, like many other IDEs (compilation + execution, using only temporary files), can be useful because it allows you to test a temporary code without saving it (neither modify existing source files of user).

Sounds like a good idea. I should have added that functionality a long time ago. :-)

[PaulSquires]

Some screenshots from latest Version 1.4.1 (August 3, 2017):







Version 1.4.1 (August 3, 2017):
- Added: Major change. New Build Configuration system.
- Added: Quick Run (added to Compile menu and Toolbar).
- Added: Option (Environment Options :: General Options) for "Ask before exiting the editor".
- Added: Check added to catch whether a loaded file has been *deleted* by something external. Message now displays asking whether to keep file open or close it.
- Change: The "Run Executable" functionality now runs the currently active source code file should the EXE exist. Previously would always run the most recently executed exe.

This release can be downloaded from GitHub (full source code and compiled exe's): https://github.com/PaulSquires/WinFBE/releases

Jose Roca continues to produce great new code for FreeBASIC Windows. Check out the help resource at http://www.jose.it-berater.org/CWindow/ ... ework.html and get the code from http://www.planetsquires.com/protect/fo ... pic=4061.0

[Carlos Herrera]

Jose Roca continues to produce great new code for FreeBASIC Windows. Check out the help resource at http://www.jose.it-berater.org/CWindow/ ... ework.html and get the code from http://www.planetsquires.com/protect/fo ... pic=4061.0

Paul,
Can you provide a simple example of CWindow use?
Carlos

[MrSwiss]

Hi Paul,

a suggestion if I may: break the Compiler and other IDE settings, out of [View]-Menu and,
add something like: [Options] or [Configuration]-Menu (as done in: FBEdit 'Options').
Searching for *Options* under the *View*-Menu, is less than intuitive (IMHO).

[PaulSquires]

Hi Paul,

a suggestion if I may: break the Compiler and other IDE settings, out of [View]-Menu and,
add something like: [Options] or [Configuration]-Menu (as done in: FBEdit 'Options').
Searching for *Options* under the *View*-Menu, is less than intuitive (IMHO).

Thanks MrSwiss, yes that sounds like a reasonable suggestion. I can see the Build Configurations going under that menu option as well (similar to FBEdit approach). When I add User Tools dialog, I would also add that to the Options menu.

Thanks,

[fxm]

Hi Paul,

a suggestion if I may: break the Compiler and other IDE settings, out of [View]-Menu and,
add something like: [Options] or [Configuration]-Menu (as done in: FBEdit 'Options').
Searching for *Options* under the *View*-Menu, is less than intuitive (IMHO).

FBIde users have no difficulty for finding that, because with FBIde, the "Settings" menu is under the main "View" menu!

[Josep Roca]

> Can you provide a simple example of CWindow use?

The WinFBE editor comes with many templates and projects.

To access the templates, click the arrow at the right of the New toolbar button.

To load a project, click the menu option Project->Open Project and select the WinFBE Sample_Projects folder.

[deltarho[1859]]

@Carlos Herrera

If you get well acquainted with Jose's CWindow you will be able to 'knock out' GUIs as if you were an expert in SDK progarmming.

[PaulSquires]

Version 1.4.2 (August 5, 2017)
- Added: "Options" top menu item and moved "Environment Options" and "Build Configurations" under it.
- Changed: Updated CWindow framework to Release Candidate 30.
- Fixed: GDI resource leak when Find/Replace dialog invoked multiple times.

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

[sancho2]

Hi Paul:
Version 1.4.2:
Quick run works from menu but the tool bar button is not enabled. Did you foget to turn it on or is it something I did?

The last time I asked about templates they were not yet implemented. I must have missed the implementation. That works really well.
I download CWindows and so far so good. Really nice.

Great stuff both WinFBE and CWindows.

Edit:
I cannot reproduce the Quick Run not working. I am not sure what happened but it is working now.

[PaulSquires]

Hi Paul:
Version 1.4.2:
Quick run works from menu but the tool bar button is not enabled. Did you foget to turn it on or is it something I did?

Is it possible that you tried to use Quick Run with a Project? It is not enabled for Projects.

Great stuff both WinFBE and CWindows.

Thanks! Great appreciated :-)

[ur_naz]

Can you add right margin to text editor and right margin width setting?

[PaulSquires]

Can you add right margin to text editor and right margin width setting?

Thanks, no problem at all. This has now been added and will be part of the next upload.