2 things:
1. thankfully I had source code backups 2. I'm very glad I documented (commented) it well with my datestamp too. I always code to help me later down the road when I lose my mind. :-)
On 7/10/2019 11:18 AM, Gene Wirchenko wrote:
At 07:48 2019-07-09, "MB Software Solutions, LLC" mbsoftwaresolutions@mbsoftwaresolutions.com wrote:
Found some code from last year that told the tale: https://www.screencast.com/t/eHBKVzcvz
I was simply removing the page after the fact in the Form.Init based on user preferences.
And you probably felt somewhat foolish when you realised that your previously-written, previous-brilliant code was the cause.
I just had that myself. Actually, I am just finishing up with that.
I had to severely hack up one of my forms handling classes. How severely?
I had to override a main method so that a bunch of other methods normally used would never be called. In one case, I had to override a method from about a page of code down to just a return statement.
Then, I found that I had removed a bit too much functionality and had to debug that.
One of my OOP peeves bit here. That is when I have to write a new subclass and have to override significant parent code. Flipping back and forth between the two classes gets old very fast.
One of the great things about OOP is that you can write a class and then forget about it. That is also one of the nasty things. (I had not looked at the class much in the past several years.)
Sincerely,
Gene Wirchenko
[excessive quoting removed by server]