WinFBE Suite 1.6.7 (July 22, 2018)

[Johan Klassen]

thanks again Paul
I am eagerly awaiting the release.

[Gregory Mayo]

Paul, finally got around to testing on Win10 desktop and again neither program would start. At least with Win7 I was informed of the crash but in Win10 just nothing. I have since found that the easiest fix to to edit the WinFBE.ini and enclose either or both compiler paths in quotes and then the will start. If you only do one, then you can go to Options and enclose the other path in quotes. As you say, there are no spaces in the path but when I found that this was causing the problem I just enclosed the path in quotes to see what it would do. A pleasant surprise when it worked. A bit of a puzzle as I doubt you have changed this code from previous releases and they all work as expected.

[Paul Squires]

Thanks Gregory - I appreciate you continuing to test.

Something Jose mentioned in a post a couple of days ago (about Chinese characters) got me looking at the source code again for the compile process. There were two functions there I coded the incoming parameters as ZSTRING when technically they should be WSTRING. I have changed the parameters and am now testing to see if it makes any difference especially with regard to wrapping the compile path in enclosed double quotes.
The two functions were: CreateChildProcess and RedirConsoleToFile.

[Paul Squires]

Something Jose mentioned in a post a couple of days ago (about Chinese characters) got me looking at the source code again for the compile process. There were two functions there I coded the incoming parameters as ZSTRING when technically they should be WSTRING. I have changed the parameters and am now testing to see if it makes any difference especially with regard to wrapping the compile path in enclosed double quotes.
The two functions were: CreateChildProcess and RedirConsoleToFile.

This was definitely a problem and since I've changed it I can now correctly run the compiler from long path names with embedded spaces (without having to enclose in double quotes - which itself would cause compile fails). I will continue to look at this but the failing compiles that I experienced earlier today have now ceased. I hope this will also fix the issue that you guys have been seeing. I will post a test 32-bit exe for you to try before I upload a full package later this evening. I'll post that exe here in a couple of hours.

[José Roca]

Since I began to work with unicode my rule of thumb is that ZSTRING no longer exists and that STRING is only useful when you want to easily allocate a byte buffer without having to use Allocate/Deallocate.

[José Roca]

Thanks Johan!
I didn't realize you were srvaldez over on the FB forum (or maybe I did and just forgot!). Awesome, thanks for sharing. Greatly appreciated

Maybe he should look at my unicode clipboard functions AfxGetClipboardText and AfxSetClipboardText (in AfxWin.inc) instead of trying hacks to return unicode in an ansi string. ( https://www.freebasic.net/forum/viewtopic.php?f=2&t=26905 )

[ChrisC]

Hello Paul

does this WinFBE superceed Firefly for freebasic?   

so shall i start with WinFBE to compile programs with Freebasic?

[José Roca]

Indeed.