WinFBE v3.0.2 (BETA-3) (October 23, 2022)

[Paul Squires]

Download link: https://github.com/PaulSquires/WinFBE/releases/tag/3.02-beta-3

**THIS IS A BETA RELEASE SO PLEASE ENSURE THAT YOU HAVE BACKUP COPIES OF YOUR CODE**

Version 3.0.2 (beta 3)
Editor:
- Fixed bug where WinFBE 64-bit only would GPF if currently loaded file is edited by an external editor causing WinFBE to reload the file.
- Fixed bug where focus would be lost from the Find textbox as the user typed a search word and a corresponding match was found.
- Fixed bug where an invalid startup position for the editor would be saved if WinFBE closed while it is minimized to the Windows Taskbar.
- Added new internal code parser that creates codetips and autocomplete popups.

Visual Designer:
- MAJOR FILE FORMAT CHANGE: Form data separated from code file and is now saved to external file with *.design file extension.
- Existing visual designer files are saved with a "*.backup-before-upgrade" file extension prior to the new file format upgrade in case something goes wrong and the user needs revert to the older file.
- When selecting a control from the toolbox and then just clicking on a form (not "drawing" it), it creates a control with a height and width of 0. There are now default sizes for all controls that may be created too small.
- When double-clicking an event in the toolbox, automatically enable that event, create the placeholder (if needed) and switch to that event in the code view.
- When double-clicking a control in design view, automatically switch to the code view for the default event handler for that control (e.g.: the _Click handler if it's a button).
- Listview was not clearing columns/rows when a form is reused (e.g. via popup form).
- Added Listview property (HeaderThemed) to enable/disable theme drawing for the header portion of the Listview.
- The ability to set the default control font name and size for all new controls created for a project, rather than always defaulting to Segoe UI 9pt.
- Added Button control property (AllowFocusRect) to enable/disable drawing the rectangle around the button when it has focus. Only valid if Theme property is False.
- Added Button control property (TextForeColorHot) to set text color when mouse hovers over the button. Only valid if Theme property is False.
- Added Control property (Anchor) which allows you to specify layout resize/movement at design time (uses the WinFBX CLayout class behind the scenes).
- Added Anchor property for Forms.
- Added ChildFormParent property for Forms.
- Added check to prevent duplicate code output into the resource file for images with the same path and filename as this would cause a compile error.
- Added code to ensure that when saving Form data it is output to the JSON design file prior to any Controls on the form, otherwise a GPF may occur when loading.
- Added code that will update or add to existing SELECT CASE event structures in generated code for MENUS, STATUSBARS, and TOOLBARS.
- Added TextBox and RichEdit control property (MaxLength).
- Fixed display of Frame control text background color in both the visual designer and code generation.

[philbar]

Hi Paul,

I'm not sure if this is specific to Beta-3, but I just ran into it. I made a little project with a button, a status bar and a menu, in that order. It compiles and runs as expected.

When I close WinFBE and come back to the project later, WinFBE64 silently crashes, but WinFBE32 opens it with no problem.

[Petrus Vorster]

Everything you added works like a charm.
No errors found this far.

64 and 32 currently giving good results.

Regards, Peter

[Paul Squires]

Thanks Phil and Peter for the feedback. I appreciate it. Phil, I will track down the source of the GPF in the 64-bit version tomorrow. It would have to be related to new code that I added over these past few betas.

[Paul Squires]

Hi Paul,

I'm not sure if this is specific to Beta-3, but I just ran into it. I made a little project with a button, a status bar and a menu, in that order. It compiles and runs as expected.

When I close WinFBE and come back to the project later, WinFBE64 silently crashes, but WinFBE32 opens it with no problem.

Hi Phil,

Could you please try this WinFBE64 EXE to see if it crashes with your project?

https://www.planetsquires.com/files/WinFBE64.zip

Thanks,
Paul

[SeaVipe]

Hi Paul,
Minor hiccup on my machine: occasionally codetips will display codetips for the wrong procedure. This usually happens the second time I attempt to fill in params. The first time it works properly but not the next and I can't always repeat this. Example: type the name of a Function or Sub with a parameter and then fill in the values. To double check that I did it right, I retype the Function's left bracket to show the codetips. This works most of the time, but not always.

Autocomplete popups usually work but now and then an unusual value will be the only choice given the leading/first letter when I know that there are more. For example, ListView, frmMain.lvMain will popup many choices. A couple of times (can't repeat this) I made the wrong choice (letter 'L' gave me 3 choices) so deleted it and tried again. This time when I typed "L", there was only 1 choice and it didn't have anything to do with a listview control (that I am aware of). I should have written it down but I didn't want to lose my train of thought. Restarting WinFBE did not resolve the issue but retyping the code on a different line did the trick.

Otherwise, codetips and autocomplete popups are working great.

[Paul Squires]

Thanks Clive, the codetips and autocomplete is practically all new code so I expect there to be hiccups. It is the primary area of code that I have remaining to test and reports like yours are welcomed.

[philbar]

Thanks Paul, that did the trick.

Phil

[SeaVipe]

Hi Paul,
One form of a multi-form project is throwing Duplicate Definition errors and is the only form in the project to do so:

The result of multiple clicks on the Click Event:

Code Select Expand

Function frmTabSearch_lvEntryType_Click( ByRef sender As wfxListView, ByRef e As EventArgs ) As LRESULT
    Function = 0
End Function
''
''
Function frmTabSearch_lvEntryType_Click( ByRef sender As wfxListView, ByRef e As EventArgs ) As LRESULT
    Function = 0
End Function
''
''
Function frmTabSearch_lvEntryType_Click( ByRef sender As wfxListView, ByRef e As EventArgs ) As LRESULT
    Function = 0
End Function

Also, I delete the duplicates and attempt to recompile and the Click event gets duplicated and throws another error.

By unchecking all Events for all controls on frmTabSearch and deleting the duplicates (not the original events and their code) the Click Events do not get duplicated and the project compiles. But then there are no Click Events to process. 

[philbar]

Hi Paul,

About the WinFBE64 crashing problem: grr.

When I tested on my laptop last night, everything seemed fine, but when I downloaded the EXE to my work computer this morning I got crashes again. It doesn't seem to like menus. I don't know what my laptop is so happy about.

I've attached a copy of a test project that I can load with WinFBE32 but not with WinFBE64.

Phil

[Paul Squires]

Thanks Clive and Phil, I will check into both issues and track down the fixes. I'll post a new beta once these are resolved.

[Paul Squires]

Hi Paul,

About the WinFBE64 crashing problem: grr.

When I tested on my laptop last night, everything seemed fine, but when I downloaded the EXE to my work computer this morning I got crashes again. It doesn't seem to like menus. I don't know what my laptop is so happy about.

I've attached a copy of a test project that I can load with WinFBE32 but not with WinFBE64.

Phil

Hi Phil, this is an odd problem because I had the same experience as you. Yesterday, I would get crashes on loading visual designer projects with WinFBE64 but then I fixed some array bounds error that triggered a GPF and it seemed to fix the problem. At least that I what I thought but I did experience one or two GPFS subsequent to that a little later. I thought in my mind that maybe I tried loading the project with an old WinFBE64 exe version. I posted the EXE for you to try, and sadly you are seeing the same random GPF.

Tonight, I tried to trigger the GPF and, so far, all my builds of WinFBE64 are not triggering it. I loaded a "bad" WinFBE64 from yesterday that I knew triggered a GPF and the GDB debugger simply reports the crash as a heap corruption.

I will keep working on this and try to at least get a setup where the GPF triggers reliably with my latest source code. I surely hope that the error is not related to the new JSON code (FBjson, that I got from the FB forum), that has a potential memory corruption issue. Most likely it is something on my end that I have overlooked.... hopefully! 

[SeaVipe]

Hi Paul,

I also had this issue and it was with the project that is causing the Duplicate Definition problem. It crashed twice before loading for the first time in Beta 3 and then loaded ok but then the dupe issue started.

[Paul Squires]

Did you try that new WinFBE64 exe download that I posted a few posts back in this thread? I think in that build that I also fixed a problem that would contribute to multiple copies of functions existing in the database. That could have been related to the duplicate issue you experienced. I'll know more tomorrow once I can do more tests. Too tired tonight to focus on it. Need daylight and a couple cups of coffee :-)

[SeaVipe]

I haven't yet, Paul, but I will tomorrow and report back.