Version 1.7.6 (August 26, 2018)
- Added: Grab handles for locked controls/form now show using red color.
- Added: BackColorHot property for Button controls.
- Fixed: Label mouse double click caused a GPF.
- Fixed: Changed all MID function code to use ** with CWSTR variables.
- Fixed: Align and/or Resize for groups of controls was not respecting the Locked status.
- Fixed: Center in form horizontally/vertically was not correctly accounting for High DPI resolutions.
https://github.com/PaulSquires/WinFBE/releases
Hi Paul
Thank you for the new updated version of WinFBE.
A quick question.
Can all properties of forms and controls be changed during runtime?
Yes, the properties can be changed at runtime. If there are any that you have trouble with them just let me know.
Hi Paul
Thank you for your feedback.
I like to define the properties for forms and controls in source code.
For example, with "Form1.MaximizeBox = False" or "Form1.MinimizeBox = False" I cannot see any changes.
It is always possible that the error is 80 cm in front of the monitor. ;)
If all properties are definable during runtime, then I create a small project and test it. If I notice anything, I'll ask again.
Ah, in that case there are a number of Form properties that I only have coded for setting at Design time. I will complete that code so that the Form properties can be set at run time. You can see this is wfxForm.inc in the WinFormsX include folder. I believe I finished setting runtime properties for the other controls. I will have these additions for you in the next WinFBE update.
Actually, this has got me thinking that I should have an additional Event that the user can set. Something like "FormCreate". That would be called during the Form's Constructor so that the user could set additional properties at run time prior to the Form being created and shown. If you look at the Form code in your Form's source code file, you will see a long list for form metadata followed by the form creation code. A FormCreate event could patch into that form creation code via the Constructor. I'll consider this as it could be quite useful.
A few issues I have noticed with the 1.7.6 release:
- Changed: Control refresh/repaint called when Text property changed.
- Fixed: Regression: Ctrl/Shift Arrow keys not moving/resizing controls in designer.
- Fixed: Regression: GPF when ListBox row selection changed.
I will upload a new package 1.7.7 later today.
Quote from: Paul Squires on August 27, 2018, 10:07:05 AM
Actually, this has got me thinking that I should have an additional Event that the user can set. Something like "FormCreate". That would be called during the Form's Constructor so that the user could set additional properties at run time prior to the Form being created and shown. If you look at the Form code in your Form's source code file, you will see a long list for form metadata followed by the form creation code. A FormCreate event could patch into that form creation code via the Constructor. I'll consider this as it could be quite useful.
I have added a new Form Event called "Initialize". This event occurs before the form loads and before the form window is actually created. At this point, the form TYPE variable exists but the actual form window handle has not been created. It allows the programmer to be able to initialize the form via code.
''
''
Function Form1_Initialize( ByRef sender As wfxForm, ByRef e As EventArgs ) As LRESULT
Form1.MaximizeBox = false
Form1.MinimizeBox = false
Form1.Text = "My Application"
Form1.StartPosition = FormStartPosition.CenterScreen
Form1.Width = 500
Form1.Height = 250
Function = 0
End Function
Quote from: Paul Squires on August 27, 2018, 02:44:42 PM
Quote from: Paul Squires on August 27, 2018, 10:07:05 AM
Actually, this has got me thinking that I should have an additional Event that the user can set. Something like "FormCreate". That would be called during the Form's Constructor so that the user could set additional properties at run time prior to the Form being created and shown. If you look at the Form code in your Form's source code file, you will see a long list for form metadata followed by the form creation code. A FormCreate event could patch into that form creation code via the Constructor. I'll consider this as it could be quite useful.
I have added a new Form Event called "Initialize". This event occurs before the form loads and before the form window is actually created. At this point, the form TYPE variable exists but the actual form window handle has not been created. It allows the programmer to be able to initialize the form via code.
''
''
Function Form1_Initialize( ByRef sender As wfxForm, ByRef e As EventArgs ) As LRESULT
Form1.MaximizeBox = false
Form1.MinimizeBox = false
Form1.Text = "My Application"
Form1.StartPosition = FormStartPosition.CenterScreen
Form1.Width = 500
Form1.Height = 250
Function = 0
End Function
Hi Paul
I saw the list of metadata. I agree with you. It is a very useful extension.
I will gladly use the extension if you implement it.
I am already looking forward to the update. Thank you for your work.
Thanks, Paul, form _Initialize() will be very useful.