WinFBE Editor and FreeBASIC Compiler (All-in-One Package) (V3.1.0 June 4, 2023)

[deltarho[1859]]

We are all getting older and I know my eyes are not what they were when I was younger.

Same here.

I cannot help regarding WinFBE log file and so on, but there is a setting in Windows 10 which you may find helpful.

Settings>Ease of Access>Display

At the top is a slider — I have mine set to 125%.

Windows title bars, menus, drop-down menus, right click context menus, message box text, desktop icon text, file lists in Windows Explorer and many other applications are all larger.

Even the text in our posts are larger and the text as I write this.

Here is a right click context menu in TextPad.

and a message box


Ok, we are only going from 8 point to 10 point, but it makes a world of difference for me. 8 point is a struggle for me nowadays.

Perhaps you are already using this. If not, give it a whirl. You won't go back to 100%.

[freniram]

Only myopic people can read these days text on displays. Oh God, well not sure if I could say it here, but there are free utilities to change windows' font size, menus, icons, etc. And you can find it in Aerowin site and advchangefont in wintools.info. It's a general trouble for every app no matters the OS. Higher resolution, smaller letters. Just DO NOT modify "System Font" or you'll loose Explorer Search functionality.

[freniram]

WinFBE does not have a concept like the FireFly Custom Controls. Sorry.

Uff It's a pitty because I had the hope it could be after founding CTRL_CUSTOM while studying in the source code and thought I could include one myself. The problem is that the picturebox control has a problem (for me) with the hot functionality and would rather use the Jose Rocas GraphCtx control in WinFBE instead of the ImageCtx (fonts and persistence, for example). Could you think of including it in future releases?

[PaulSquires]

You can still use Jose Rocas GraphCtx control in WinFBE by directly #INCLUDE'ing it in your code. Granted, you lose the ability to drag and drop as a visual designer control but at least you still have access to being use the control and modify its code however you see fit.

[freniram]

You can still use Jose Rocas GraphCtx control in WinFBE by directly #INCLUDE'ing it in your code. Granted, you lose the ability to drag and drop as a visual designer control but at least you still have access to being use the control and modify its code however you see fit.

Ahhh, I see. I will try it. I'd read a José Roca's post where he explained that you could have the VD or the old good SDK programming way to do it, and understood that couldnt be together. Thank you. Let's give it a try.

[wallyg]

I have finally used the symbol for the split screen at the top right of the edit window. It works fine, thank you for this option. But I was wondering if it was possible for the upper and lower screens to not use the same file. I would like the top screen to be one file (containing the type definition) and the lower screen to be the file that contains the Constructor/Function/Sub/Property code. If I have missed how to do that, I am sorry but how?

Wally

[PaulSquires]

...I would like the top screen to be one file (containing the type definition) and the lower screen to be the file that contains the Constructor/Function/Sub/Property code. If I have missed how to do that, I am sorry but how?

Sorry Wally, that is not possible. The split functionality only splits the current file's buffer. It can not display different buffers from different files.

[xiaoyao]

Some BUG comments and new feature suggestions for Winfbe

1. When you open it for the first time, you should add an automatic language recognition system.
Private Declare Function GetSystemDefaultLCID Lib "kernel32" () As Long
GetSystemDefaultLCID=2052, representing China, automatically selects chinese.lang
2. There are too many steps to select Language. It is best to put it in the menu Tools》Language》chinese
3. New Project and Open Project functions should be added to the first menu. It is inconvenient to place the project main menu in the 5th item.
4. The code format is best to use UTF-8 encoding by default instead of ANSI format, otherwise the UNICODE characters in Chinese and other countries will not be displayed.
5. The Msgbox function is not supported by default. I wonder which header file it is in? It is best to add a module management function,
Module file function (supports Chinese), list of main functions of the module. These data are written into SQLITE and can be automatically searched at any time when needed.
For example, if I enter the VBCRlf function, I will be prompted whether I need to quote: vbcompat.bi.
The automatic detection function will be added later. If vbcompat.bi does not use any functions, the file will be automatically excluded during compilation.
vbcompat.bi vb6Function vbcrlf,***
6. It is best to add a WINDOWS api list, so there is no need to reference it. What APIs are used in the project? An API list module file will be automatically generated during compilation: Project_api.bas
7. Like VB6, if it supports adding OCX controls, COM DLL references, and TLB file references, it will basically be perfect.
8. It would be better if a more advanced menu mode can be designed, which can display several times the number of menus. For example, it can be composed in the form of a form, which is usually hidden and then displayed when the menu is called out.
In this way, you can display the form and code by right-clicking in the code area, go to the definition, and select the event: form1_load, Form1_click
9. You can switch between code and form freely by double-clicking, which is very convenient.

[xiaoyao]

. How to call API? From visualFBeditor ,visual Freebasic ide:

No need to declare it first like VB6. Just use it directly. If there is a form in visualFBeditor and the framework is referenced, there is no need to additionally reference WINDOWS.BI or #include once "SysUtils.bi". It is already included.
But if it is a small program with a single file, you need to #include once "SysUtils.bi". Such as #include once "WINDOWS.BI". In order to use the Windows API

[ilya-master]

I am using winfbe on windows 7 x64. Autocompletion does not work for me (only data types after the word "As" work). Everything is enabled in the settings.
Interface symbols (arrows) are not displayed yet. In the source code, they are specified in unicode (like "\u23f4"). I changed the interface font (to iosevka) in the source code, which supports these characters. But it didn't help. Instead of arrows, there is still an empty square.