Another problem is that, even if you make the dialog modeless, as it is wrapped into a function it won't return control to the main application until you close the dialog and the functions ends, so you will have to use it in another thread, and who knows how many more complications. IMO the purpose ...

It won't work. What you have to do is to make the dialog modeless: remove the EnableWindow calls in the function.

This may cause other problems, like having the input box ending being displayed behind the main window, having more than one input box active...

AxInputBox uses its own window callback procedure and message loop. Therefore, while it is in execution, the parent window can't send messages to it because its message loop is inactive. Your Sendmessage(hInputBox, WM_CLOSE, 0, 0 won't be executed until the input box dialog is closed.

FreeBasic dynamic strings aren't compatible with Visual Basic. The functions return a string, but VisualBasic does not know how to deal with it. You may need to return an OLE unicode string (aka BSTR) allocated with SysAllocString.

FreeBasic's OPEN statement does not support Unicode filenames.
You can use my CFileStream Class: https://github.com/JoseRoca/WinFBX/blob ... ss.md#Read

This is not O2, it is FreeBasic. declare function CreateWindowExA(byval dwExStyle as DWORD, byval lpClassName as LPCSTR, byval lpWindowName as LPCSTR, byval dwStyle as DWORD, byval X as long, byval Y as long, byval nWidth as long, byval nHeight as long, byval hWndParent as HWND, byval hMenu as HMENU...

Why do you declare it as a pointer if it is not a pointer? dim static1_id as integer static1_id = 500 and when you pass it to CreateWIndowEx, do te casting static1 = CreateWindowEx( 0, "static", "" , WS_Border or WS_VISIBLE Or WS_CHILD , 10 , 10 , 100 , 100 , hWnd, CAST(HMENU, st...

It's not your fault. The problem is that the GdiPlus headers for 32-bit are a mess. It was not wise to implement widely used GDI structures as classes using the same names.

For WinFBE/WinFBX, this only affects the 32-bit version. The fix is to either remove the 'using GdiPlus' statement from "Afx/AfxGdiPlus.inc" and then fix all the places in code using a fully qualified GdiPlus.symbol. Or fix all the places in code that should actually use the global RECT (...

> but maybe something i have to get used to or maybe there's an option to turn it all off but anyway. Yes. In the Menu Options --> Environment Options, you can choose what you want to enable or disable. For example, uncheck Enable Autocomplete. > i never use F5 and ALWAYS 'quick run' for testing whi...

@Paul Instead of having two separate options, what you could do is that, if the user presses F5, check first if it is an untitled/unsaved file and, if it is, call the code for the quick run option. This is what I did in the CSED editor for PowerBASIC. Of course, someone will complain about the edito...

Many users write applications instead of only test snippets of code, and for an application to be useful it needs to be compiled as an executable file. Both WinFBE and fbc are executables. How would you use them if they weren't?

> Why press three keys when you can press one? eg like FBIDE and just hit F5 for quick run. Because F5 is already assigned to the Build and execute's option, that both the author and other users use more frequently. It is an editor for Windows, and Windows' programmers use more often a GUI that the ...

With build and execute (F5). If you don't recompile the code, how are you going to test the changes that you make?

> Quick run should be F5 as that is the most used thing. :)

Not by everybody. I never use it.