Quote:
Originally Posted by the_waiter
I posted a request to Audacity forum. Maybe the developers will answer
|
Thanks for filing this
I see it was already a issue known to them,
Bug 1534. I see it effects multiple window managers as suspected.
Like I said above while I do think a patch to audacity could indeed fix mokshas issue here, the very fact that e22 goes ahead and displays it (correctly) indicates that we (ie Moksha) could handle this better on our end. Just unsure at the moment where in mokshas source code I should look for this error. Step thru audacitys source code and follow the threads until I end up in e17 code for window management? Or add breakpoints in Mokshas code at suspected spots dealing with window display and see if audacity triggers any of them displaying this and go from there. Or what was that I did with strace and pcmanfm debugging that menu cache issue? Or ....
It all sounds tedious.
Any Ideas anyone?
Patches gladly accepted, lol.
Even if the audacity devs fix this on there end and I repackage the application it is still an issue hidden until triggered by another piece of code doing the same sorta thing. As I mentioned above, googling around shows other apps which had similar errors but fixed it. ANy apps with similar errors around that have not fixed it or even don't know about it?
A great unknown.
