Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

....yeah, it was waaaaaaaaaay too wide :-)

I will check that out. I did increase the label sizes in order to allow for language translations that are longer than English. It could be that my calculations were off.

Hi Paul,


In the menu editor the State: Checked checkbox, checkbox is disabled or covered by another control so to modify Check/UnCheck the CheckBox must be clicked on the right of the control not in the actual CheckBox itself. The label for "State:" might be partially on top of the CheckBox.

Thought you might want to check that out ;o)

Version 1.8.6 (December 7, 2018)
- Added: Localization file creation and editing. "Options" / "Environment Options" / "Localization".
- Added: Check to prevent duplicate menu names that would result in a compile time error.
- Changed: Removed the Environment option to specify the WinFBX chm help file. WinFBX help is now displayed using the markdown help browser.
- Fixed: With AutoIndentation enabled, ELSEIF will now line up correctly to the parent IF/THEN headers.
- Fixed: Background transparency of several Up/Down png graphics used within the editor.
- Fixed: GPF for new Forms created since version 1.8.5. This was a regression in 1.8.5.

https://github.com/PaulSquires/WinFBE/releases

I've tried the menu editor in designer, - graphically it works OK, but I was expecting some code stubs to be generated for each item on selection, similar to items in toolbox.

Whenever a Main Menu exists on a Form, two message handlers are always created automatically: Click, Popup. Those handlers will always be generated even if you delete them from the code editor. Refer to the Help file topics under Main Menu called "Responding to a Menu Click" and "Initializing Menu Items before they are shown".

Nothing happens, as far as I can see, for toolbar editor, or status bar editor. Have I not installed it correctly, or is this as it should be at the moment?

I don't have those implemented yet. Per Help file Visual Designer / Overview.

About Menu Designer:
- Can produce two or more entries and get the same name, for instance Help.
- Unable to get access to entry shortcuts.
- Unable to get access to Checked.
- When trying to compile and run WinFBE stops...
[Edit]:
- Unable to compile.

Thanks Dennis, I will add check to detect duplicate names.
You can only get access to the shortcut keys and the checked property for menu items that are sub items. Basically, in the Menu Editor you need to indent the submenu items by highlighting the entry and pressing the right arrow icon.

A bit different from previous versions, afaik. If I create new project, then go straight to designer, add new form, it shows designer window, with first line (pointer), then after a few seconds winfbe crashes. Ok if I create a new basic file first.

Hi Paul, I'm experiencing similar results as Ray but I get a crash regardless of whether or not I create a basic file first.

Thanks guys, this was a little harder for me to track down but I found it. It only affected new forms that had not been saved. I will get an update posted soon.

About Menu Designer:
- Can produce two or more entries and get the same name, for instance Help.
- Unable to get access to entry shortcuts.
- Unable to get access to Checked.
- When trying to compile and run WinFBE stops...
[Edit]:
- Unable to compile.

A bit different from previous versions, afaik. If I create new project, then go straight to designer, add new form, it shows designer window, with first line (pointer), then after a few seconds winfbe crashes. Ok if I create a new basic file first.

Hi Paul, I'm experiencing similar results as Ray but I get a crash regardless of whether or not I create a basic file first.

I've tried the menu editor in designer, - graphically it works OK, but I was expecting some code stubs to be generated for each item on selection, similar to items in toolbox. Nothing happens, as far as I can see, for toolbar editor, or status bar editor. Have I not installed it correctly, or is this as it should be at the moment?