Hiya That's the problem.
I can't figure out how to create a subclassed version of a textbox for instance in the first place.
If I want to set every textbox in the system to 10pt I don't want to edit every control on every form to change the font size. I would just want to change it in the textbox base and compile.
The only way I can find in the help docs is to create a new usercontrol and put the textbox inside a usercontrol. Every form then has the new usercontrol and not a direct textbox. This seems like a right pitb
What am I missing?
-----Original Message----- From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of Stephen Russell Sent: 18 August 2021 17:12 To: ProFox Email List Subject: Re: [NF] Winforms
You could create a project where you subclassed any form widget in your way.
Then in every new solution, you include that project and use those classes at the top instead of: using System.Windows.Forms.Form
you would use : using MyUberCoolSystem.Windows.Forms.Form
Just like you had to do in VFP as I remember.
I would never do that again, personally. If I need to override something I'd do it in just this application, and not everything I did. Extending the functionality of classes is easy as needed. In all of my data objects, I override the ToString() to output a serialized json string of the data.
On Wed, Aug 18, 2021 at 7:04 AM Alan Bourke alanpbourke@fastmail.fm wrote:
It's been many years since I used WinForms but if I remember visual inheritance and WinForms designer support in Visual Studio don't work the same as you would be used to from VFP or VB6. Basically you have to programmatically add designer support, or as you say programmatically update any control properties you want to change.
WPF and its successors are much better in this regard.
[excessive quoting removed by server]