So I see that in going from 2.8.5 to 3.0.0 you fixed a memory leak.
My sub just ran out and what I am gathering is that I will need to spend a minium of 150 bucks to fix said memory leak (which my app is clearly suffering from.)
I get that as the Navigator develops and gets new features and such that a new subscription gets you new stuff and fixes little quirks here and there... But to have to pay to fix something like a memory leak from one version to the next seems a bit steep...
I have been a huge proponent of your work to the degree that I know multiple developers that have purchased your toolkit based on my advice but payment to fix a memory leak one version up... *sigh* I hope their subs didn't end or I will get an ear full.
I don't want to hear from the fanbois that this is normal becuase A: It isn't, every example you give me I can give you 10 where this type of bug would have been addressed seperately B: I was fully intending on purchasing a new sub but I am at least 4 months out from a new dev cycle and C: I am a full fledged member of the krypton fanboi association so take a seat, I still love Phil's work.
I could see my way to upgrading sooner if there was some tangible upgrade, but out of the top community requested controls (DateTimePicker, ScrollBars, TreeView, DataGridView enhancements) you added 0.
I would rather wait the 4 months (to get 16) and see what happens but now I may just complete the plunge over to WPF.
You hear me squakin' big chicken?