I just installed FB-1.03.0-win32 last week. As with each update, new errors are revealed in old code that previously worked. This is a good thing, of course, since it improves my code. A nasty error showed up, however, that I think is worth mentioning to the FB community. My code has a shared uinteg...

This is a GREAT tool, especially for custom fonts, but it requires modification (beyond my skill set) to run in 64 bit. The problem is the namespace gdiplus does not get set up when the ifdef__FB_64bit__ is executed in GdiPlus.bi. Here's the code #ifdef __FB_64BIT__ #include "gdiplus-c.bi"...

Ah, I didn't realize the linker to create 64 bit executables would not be backwards compatible with 32 bit compiled libraries.

Guess I will need to hunt down the source code and recompile the library.

With the win64 version I'm having a problem with the linker. Linking fails with ld.exe: skipping incompatible C:\FreeBasic-1.03.0-win64\lib\win64/libxfont.a when searching for -lxfont ld.exe: skipping incompatible C:\FreeBasic-1.03.0-win64\lib\win64\libxfont.a when searching for -lxfont ld.exe: skip...

@ AstroJohn,
Do you mean this FB_GUI?

[url]
viewtopic.php?f=8&t=12592
[/url]

I wrote that code and have made several improvement, but haven't updated in a loooong time. I'm still using it in our lab. Works fine.

BasicScience

Thanks. Confirmed, GetConsoleWindow works.

Is there a method to have an executable file created with FB (console mode only) run without creating an icon in the Win Taskbar?

Here's the instruction to make the background transparent with xFont. For many graphics functions, magenta = rgb(255,0,255), is used to designate transparent.

@MOD

Your suggestion worked. I can't thank you enough. I really appreciate your input to the Forum.

@MOD. Thanks, the 0.91.0 build does indeed fix the PMAP bug. Compared to build 0.90.1, however, I get new errors for a piece of code I grabbed to copy/paste to the clipboard. I'm not very experienced with the WIN API, so I'm having trouble fixing these two errors: error 41: Variable not declared, Rt...

Is there an easy way to get the coordinates of the Viewport and the Window scale factors? If these numbers were available, then a custom PMAP replacement function could be written by the user while waiting for the next release of FB.

OK, thanks

The PMAP function does not appear to work correctly in FB 0.90.1 when the screen scale is changed with WINDOW. This code does work in FB 0.24.0. The correct responses for the PMAP responses are 1 and 400, but FB 0.90.1 gives 1 and 800. ScreenRes 800, 600, 32 Print "Default coordinates (0,0) - (...

Works beautifully. I especially like the arbitrary font load feature.
Thanks.

Got it, thanks.