PlanetSquires Forums

Support Forums => WinFBE - Code Editor and Visual Designer => Topic started by: Paul Squires on February 18, 2020, 05:59:11 PM

Title: WinFBE Suite 2.0.4 (February 18, 2020)
Post by: Paul Squires on February 18, 2020, 05:59:11 PM
Version 2.0.4 (February 18, 2020)
- Added: UpDown control.
- Changed: StatusBar Panels are now OwnerDraw which allowed for defining Fore/ForeHot/Back/BackHot Colors, on a per-Panel basis.
- Changed: Use of StatusBar BorderStyle is now deprecated as it has no effect in WinFBE programs where Windows Themes are enabled.
- Changed: StatusBar Panel ToolTips now act like regular tooltips and are not restricted by the limitations per the SB_SETTIPTEXT Win32 message documentation.
- Changed: New Chinese lanuage file thanks to ganlinlao.
- Fixed: Regression in WinForms code whereby KeyDown, KeyUp and KeyPress fired twice instead of once.
- Fixed: ListView possible GPF when invoking Items Clear method (disabled redraw of ListView to prevent accessing a now deleted Item).
- Fixed: The Width and MinWidth properties of StatusBar Panels were not being generated in code correctly.
- Fixed: StatusBar Panels with AutoSize set to Contents were not calculating space needed for any associated Panel image.
- Fixed: StatusBar Panel with AutoSize set to Spring can now be any panel (not just the last panel). However, only one panel can be designated as Spring.
- Fixed: An assigned Button control Image would not necessarily display the correct size at design time.

https://github.com/PaulSquires/WinFBE/releases
Title: Re: WinFBE Suite 2.0.4 - Early Observations
Post by: SeaVipe on February 19, 2020, 01:40:04 PM
Thanks, Paul!
A few early observations:
See the attached image for the result of compiling an existing (WinFBE 2.0.3) Visual Designer 64 bit project with StatusBar. Labels and ListBoxes appear on the compiled form but are blank.
New Visual Designer Win64 Console (Debug) project.
-Menu and StatusBar editors do not generate code until the form is saved, compile will fail without manually creating it.
-Adding a StatusBar;  Labels and ListBoxes appear but are blank. StatusBar appears to be involved.
-StatusBar cannot be removed.
-MainMenu can be removed but Visual Designer still displays a blank white area where the menu was. Left Click the white area pops up the menu editor which is (correctly) un-populated. Compile and Run and the application's Main Menu area is clear.
To fully remove Main Menu, ToolBar and StatusBar: in the individual editors, UnCheck "Display on form" then remove all related code - then save.
Once the StatusBar is fully removed, Labels and ListBoxes display properly.
-ToolBar. Cannot get Child forms to display.
Title: Re: WinFBE Suite 2.0.4 (February 18, 2020)
Post by: Paul Squires on February 19, 2020, 02:19:53 PM
Thanks Clive - I am working through your list now and hope to have some better answers soon.
The picture that you posted is showing warnings generated from Jose's CSafeArray code? In the 2.0.4 update I used Jose's very latest version of his code from GitHub. Were you getting that error in 2.0.3?
Title: Re: WinFBE Suite 2.0.4 (February 18, 2020)
Post by: SeaVipe on February 19, 2020, 02:30:02 PM
Hi Paul,
QuoteWere you getting that error in 2.0.3?
I did not get that error in 2.0.3.
I've been testing 2.0.4 with an older test project that has one of every control up to 2.0.3 and I get the same warning.
Title: Re: WinFBE Suite 2.0.4 (February 18, 2020)
Post by: Paul Squires on February 19, 2020, 02:32:30 PM
I have the StatusBar/Label/ListBox issue fixed. Stupid error on my part, of course.
I will do the MainMenu issue next.
Title: Re: WinFBE Suite 2.0.4 (February 18, 2020)
Post by: Paul Squires on February 19, 2020, 03:14:33 PM
Just made this change:
If no valid Menu items exist then "Display on Form" checkbox in the Menu Editor is cleared and no menu code is generated.
Title: Re: WinFBE Suite 2.0.4 (February 18, 2020)
Post by: Paul Squires on February 19, 2020, 03:20:04 PM
QuoteTo fully remove Main Menu, ToolBar and StatusBar: in the individual editors, UnCheck "Display on form" then remove all related code - then save.

Yes, that's right. Each of the editors generate boilerplate code for events to handle Clicks, etc. Those event handlers have parameters containing objects associated with menu, toolbar, statusbar that has not been generated (because the underlying control has been removed).
Title: Re: WinFBE Suite 2.0.4 (February 18, 2020)
Post by: José Roca on February 19, 2020, 04:56:24 PM
The latest FB compiler was giving me unexpected errors with CVAR even when it was not used and only included. I have added a couple of constructors that seem to fix the problem, at least for now.

The attached file contains the modified file.
Title: Re: WinFBE Suite 2.0.4 (February 18, 2020)
Post by: SeaVipe on February 19, 2020, 06:01:25 PM
Thanks, José, that fixed the CVAR errors I was getting.