WinFBE BETA 5 - update and news

[Paul Squires]

Hi everyone,

I have ditched the FB version (fbJSON) code that I was using to read the new JSON visual designer file format. There seems to be a subtle stack overflow issue in that code somewhere that triggers a random GPF. Honestly, I ran out of patience trying to troubleshoot it and it might have been related to the problem that I describe below in this post. Too late now because I have already switched to the CJSON parser.

I have implemented a rock solid, battle tested, JSON parser from https://github.com/DaveGamble/cJSON
I have compiled both 32 and 64 bit versions of that JSON dll and have translated the header file for my purposes. It works perfectly and is extremely fast.

While working with CJSON dll, I found out that I have a slight error in the JSON that I am outputting to the disk file for EVENTS. I was adding an extra "," comma immediately after the EVENT name. This is not correct JSON and I have since corrected the problem.

HOWEVER... the CJSON dll will not read existing WinFBE files created in earlier BETA's that have EVENTS outputted to the file (because of that extra "," comma problem).

When I release BETA 5, you may have to manually edit your form design disk files to remove the extra commas next to each of your EVENTs. It is not hard to do, but it could be tedious. It will be a one time thing so I am not adding code to WinFBE to automate this. If you run into trouble then you can email me your design file (or post it here on the forum) and I will edit it for you. Nothing is lost in your design file, it just will not load because of the extra "," commas.

I'll explain all of this again once I upload BETA 5. I just have one more bug that I want to fix first. It seems that if there is an error in the WinFormsX code and you attempt to do a compile, then the designer JSON file will get saved WITHOUT all of the form and controls data. That is a nasty bug that must be fixed because it could happen if you update the WinFBE EXE but have older WinFormsX files.

[Johan Klassen]

and cJSON's license looks much simpler 

[Joerg B.]

Hello Together

The described "problem" with the .design files could be solved quite easily via the page "https://jsoneditoronline.org/".
I uploaded the corresponding files to the site, selected the tree view, repaired the file and then had it saved back.
Before that, of course, I made a backup.
At least for me, I was able to read and compile the files in the current version via Github without errors.

Maybe this helps one or the other of you.

It's worth a try before you drown all Paul with a conversion.

[Paul Squires]

and cJSON's license looks much simpler 

Thanks for the reminder! I did not re-include the actual license text back into the file once it was ran through fbfrog to help with the C header conversion.

[Paul Squires]

Hello Together

The described "problem" with the .design files could be solved quite easily via the page "https://jsoneditoronline.org/".
I uploaded the corresponding files to the site, selected the tree view, repaired the file and then had it saved back.
Before that, of course, I made a backup.
At least for me, I was able to read and compile the files in the current version via Github without errors.

Maybe this helps one or the other of you.

It's worth a try before you drown all Paul with a conversion.

Awesome! Thanks Joerg! Yes, that is a great (and easy) way for people to modify their design file and it would certainly alleviate some extra work for me.