WinFBE FreeBASIC Editor for Windows
WinFBE Suite includes integrated editor/compiler/tool suite. It contains the latest WinFBE, latest FBC compiler and support files, latest WinFBX (Jose's Afx includes), User Tools, and Help files. Everything is pre-configured so you should be able to simply download the archive (WinFBE_Suite.zip), unzip it, and start either the 32 or 64 bit version of the editor, compile, and success. A separate Windows Installer (winfbe_suite_setup.exe) package also exists if you prefer to use an installer rather than simply unzipping the archive. In both cases, it is recommended that you install into a folder whose name does not contain spaces because sometimes embedded folder spaces can cause compilations to fail.
https://github.com/PaulSquires/WinFBE/releases
Full source code and binaries are available at: https://github.com/PaulSquires/WinFBE
Release versions are available at: https://github.com/PaulSquires/WinFBE/releases
Code is written using the FreeBASIC language and uses the Scintilla editing library (in DLL form).
Features:
- Unicode enabled.
- 32 bit and 64 bit versions.
- High DPI aware for any monitor resolution.
- Language localization. Simple create language file based on English.lang file.
- Localized for many languages.
- Projects and non-project based editing.
- Easy integration of Console or GUI based code.
- Incremental compiling of code defined as a "module".
- Easy including of Windows Resource files simply by specifying which source code file is the resource.
- Seamless integration of the FreeBasic Compiler (both 32 bit and 64 bit).
- Codetip popups and auto completion.
- Built in Visual Designer.
Requirements:
- Windows Vista or later operating system. Windows XP is not supported because many newer API's are used in the source code.
Resources:
- Jose Roca: WinFBX library. Get it from https://github.com/JoseRoca/WinFBX
- Visit http://www.planetsquires.com/protect/forum/index.php for support forum.
The WinFBE editor is licensed under the GNU GPLv3 or later.
(https://www.planetsquires.com/images/dark1.png)
(https://www.planetsquires.com/images/light1.png)
(https://www.planetsquires.com/images/winfbe-vd.png)
Thanks for the update Paul. Looks good. I will give it a whirl. Is there any way to view the toolbar as was available earlier versions?
Thanks, Paul!
I downloaded the zip file, renamed my existing WinFBE_Suite to WinFBE_suite.3-Beta-3 and unzipped v3.0.0 to C:\WinFBE_Suite. Then copied (from WinFBE_suite.3-Beta-3) WinFBE.ini and user_snippets.ini to the new Settings folder and dark.theme to the new themes folder - works great and my theme settings and projects list and snippets are all correct...
Hi Paul.
First of all, thanks for the shiny new update. WinFBE/WinFBX has been and remains my favorite way to make Windows programs.
Second, here are two things that I really, really should have noticed when you were doing betas. I don't know where my attention was.
A) If I start a designer project, add one or more forms and then use Save All to save them, the Form.inc files don't show up in the Explorer. Doesn't happen if I save them individually. If I close WinFBE and re-open the project, they still aren't in the Explorer. See the picture.
B) If I modify one form, then modify the other form, then switch back and forth between forms, the unsaved indicators on the tabs go away.
Hi Paul, The Designer Menu is mostly greyed.
Also...
Old issue with Designer not able to scroll to the bottom of Forms higher than 885 pixels.
I have found that scrolling to the bottom of a form higher than 885 pixels and then manually setting the height to < 885 pixels and then grabbing the now visible resize grabber and dragging it down to 885 pixels (where it stops increasing the height) will display the bottom of the form and the StatusBar (which so far has not been visible). Perhaps there is a limit to the height of a form? My monitors can display forms higher than 885 pixels.
For when you start working on the Designer!
I love the feel of this, and everything looks bright and "crisp" (due to a lack of a better word)
I just want to start something new right away.
While we are not having the Auto-resize of controls yet, i was hoping to learn how that worked and perhaps do it manually.
From my understanding you have a list of the controls, their locations and the original form size.
Then on the WM_size you retake the from size and move the controls again in relation to those new parameters.
I get the feeling its not going to be as easy as it sounds.... ;-)
Regards,
Peter
Quote from: James Klutho on May 24, 2022, 05:04:09 PM
Is there any way to view the toolbar as was available earlier versions?
Hi James, sorry but the Toolbar is gone, never to be seen again in the same vein that editors like Visual Studio Code has done away with them. WinFBE now has extensive keyboard shortcut support as well as you being able to click on the various panels in the statusbar that will pop up the related function.
Quote from: philbar on May 25, 2022, 11:35:26 AM
A) If I start a designer project, add one or more forms and then use Save All to save them, the Form.inc files don't show up in the Explorer. Doesn't happen if I save them individually. If I close WinFBE and re-open the project, they still aren't in the Explorer. See the picture.
You are correct and I have been able to re-create this problem with the "Save All" on new Forms. I will fix it.
Quote
B) If I modify one form, then modify the other form, then switch back and forth between forms, the unsaved indicators on the tabs go away.
I have not been able to duplicate this behaviour yet. I'll keep looking.
Quote from: SeaVipe on May 25, 2022, 10:10:25 PM
The Designer Menu is mostly greyed.
Thanks Clive, yes that does seem to be a problem that I will fix.
Quote from: SeaVipe on May 25, 2022, 10:21:03 PM
Old issue with Designer not able to scroll to the bottom of Forms higher than 885 pixels.
Thanks! Yes, this has been a long standing problem with the visual designer that I really to fix... finally. :-)
Quote from: Petrus Vorster on May 26, 2022, 06:16:32 AM
I love the feel of this, and everything looks bright and "crisp" (due to a lack of a better word)
I just want to start something new right away.
While we are not having the Auto-resize of controls yet, i was hoping to learn how that worked and perhaps do it manually.
From my understanding you have a list of the controls, their locations and the original form size.
Then on the WM_size you retake the from size and move the controls again in relation to those new parameters.
Thanks Peter :-)
Your approach to resizing controls is correct. It is not that difficult but it can be cumbersome especially if you have a lot of controls that need to be resized and/or repositioned. If you run into trouble then be sure to post. Sometimes people get confused when positioning controls and getting the relative window based coordinates confused with the screen coordinates (and then also being able to convert back and forth between the two). I also create one function for each Form that houses all of the resize code and I call that code from the Form's main load event and also the Form's Size event. This prevents code duplication.
@Petrus Vorster:
Forgive me for butting in, but for resizing you might want to look at the Clayout control in WinFBX. It works very well, and I think it deserves to be advertised. Check out the layout manager programs in the templates.
In order to use it in a Designer program, you have to come at it "sideways" because everything in the examples happens in the main program, but everything in a designer form happens in an event function. Basically, you just create the layout control and attach it to your form in Form_Load. Then for each control on the form you specify that this one is anchored to the left edge and it scales only by width, that one is anchored to the top and it scales by width and height, etc. Then in the Form_Resize event, you just call the AdjustControls member of the layout control. When the form closes, you delete the layout control.
If anyone is interested, I can post a sample Designer program that uses Clayout to auto-resize.
Yes mate, please do!
-Peter
I recon I will post a lot of questions soon.
The WFXTextbox control has a bunch of neat features.
But I don't see a MaxLEN setting.
That is something I use extensively , especially in the SMS platform I made for work.
Would you need to add code to each of those controls Keydown events or am i just overlooking the obvious?
Regards,
Peter
@philbar,
QuoteIf anyone is interested, I can post a sample Designer program that uses Clayout to auto-resize.
Yes, please!
Paul, I narrowed down my problem with the unsaved markers disappearing from the tabs.
It only happens in designer mode when the only change I make is to rearrange the controls on the forms. Then clicking tabs or sometimes just mousing over them makes the spots go away. If I make any change to the actual code the spots are perfectly stable.
1) When I add a new form to the project, and then decides to remove it from the project it crashes the Framework.
Also, can someone tell me how to set the maximum input length on a Textbox?
I do not see a MAXLEN setting under the properties of the textbox.
-Regards, Peter
I will have to add a MAXLEN type of property for the TextBoxes. You can do it in code as follows. This limits the textbox to 10 characters.
''
''
Function frmMain_Load( ByRef sender As wfxForm, ByRef e As EventArgs ) As LRESULT
sendmessage( frmMain.Text1.hWindow, EM_SETLIMITTEXT, 10, 0 )
Function = 0
End Function
Thanks to everyone who has reported issues and bugs with the latest release. I will work on fixes and also start enhancing the visual designer. Keep posting any issues that you find.
Tabcontrol tab images are a problem.
Attaching an Image to tab1 is no problem.
Tabs thereafter causes quite a few crashes.
Once I attach the image, the WINFBE crashes immediately.
Once restarted, and i can go back, then attaching the image is no problem.
This happened with .PNG and .iCO files which contains 16x16 up to 128x128 image sizes.
I have not checked with single ICO files e.g. 24x24 alone yet.
This happens with any additional tab.
-Peter
Thanks Peter, yes, I can confirm that attaching images to Tab Control tabs is causing a crash. I will fix.
Quote from: Paul Squires on May 30, 2022, 09:52:26 AM
Thanks Peter, yes, I can confirm that attaching images to Tab Control tabs is causing a crash. I will fix.
This was a very subtle bug to find and fix but it is now corrected. See this thread: https://www.planetsquires.com/protect/forum/index.php?topic=4609.0
Here's an odd but not critical behavior:
If I press the TAB key while in design mode (I wanted to see if focus would jump to the next control in tab order), the display jumps to the code window and inserts a TAB wherever the cursor happened to be. The design/code tab at the bottom remains focused on design.
The same thing happens if I press TAB while typing Notes (nice feature, by the way).
Obviously, the workaround is "don't do that," but it surprised me.
Thanks for the report. I will look into it and prevent such behaviour.
Quote from: philbar on June 01, 2022, 10:31:11 AM
Here's an odd but not critical behavior:
If I press the TAB key while in design mode (I wanted to see if focus would jump to the next control in tab order), the display jumps to the code window and inserts a TAB wherever the cursor happened to be. The design/code tab at the bottom remains focused on design.
The same thing happens if I press TAB while typing Notes (nice feature, by the way).
Obviously, the workaround is "don't do that," but it surprised me.
This problem should be fixed now. Check out the latest 3.0.1 update in the other thread.