Darn Obscure Framework Changes

[GWestphal]

I have a piece of code that's about 3 years old that uses a particular real-time framework. Well, over the past few years the framework has gone through a few revisions. I just spent the past 8 hours trying to debug my legacy code which is seg faulting in the new framework even though it's very simple, but the framework dev failed to note that they had removed the automatic ui initialization and it now required an additional call....*Sigh* so many hours wasted just to add one line to the constructor.

 

[Leros]

You don't have to upgrade to the new framework if the old one was doing what you need. Don't waste your time.

 

[KLin]

You don't have to upgrade to the new framework if the old one was doing what you need. Don't waste your time.

Perhaps the new framework has new features he needs to use elsewhere in the app?

 

[GWestphal]

The new framework had stability fixes that I need.