I'm looking at my latest program, taking a step back, and it looks like I'm still thinking old fashioned procedural programming which I've been doing for decades instead of new Event-Driven OOP design.
All my methods are in Form1 (except for a msg class I made). The method names look like procedural programming methods that "do things"
// FORM1 - STARTUP,END
// FORM1 - UPDATE FIELDS
// FORM1 - BUTTONS
...(lots of buttons)
// FORM1 - TIMERS/CLOCK
// SERIAL PORT DEVICE
The one thing I think I did half right is create a new instance of a msg class every time I want to send a message
Msg m = new Msg(themsg);
But even then I'm calling PortSend
to send the message, instead of something like m.Send
(Well how can a message send itself? It needs to go to the port.)
I have an entire bookshelf of books on C# and Java and I've read them all, but it appears I still think Procedure Programming. I've tried searching Amazon for more books but all I find is more of the same.
So any good books on getting me to think OOP & Event Driven instead of old fashioned Procedural Programming? Something like "Event-Driven OOP Programming for Old Fashioned Procedure Programmers"
Or maybe I need to see some big example programs that show how the pieces work together, because all I ever see is code snippets showing how to "do specific things", which I then end up using in the old fashioned procedure way of "do this, then do that".