We upgraded macholib today since that seemed to be necessary to get py2app to work successfully with MySQLdb.
But now, our (OS X) app is showing partial scrollbars in its TextCtrl fields. This is the case even when there isn't enough data in them to merit a scrollbar. Moreover, it persists even when we set the style to 0 -- which, from my reading of the docs, should make it a single-line EditField with no scrollbars.
What's really weird is how inconsistent it is. Open the window one time, and some of the fields show the problem. Close it and open it again, and different ones (or sometimes none of them) show the problem.
The problem never occurs on another machine, where we haven't upgraded macholib.
Any idea what's going on here, and how I can work around it?
An additional data point: in another window, where we were not setting the height of these TextCtrls (but were instead just accepting the default height), the problem occurred every time. When we overrode that and set the height to 20, the problem mostly went away -- now it just sometimes happens on some of them, as on the other window (that was already using heights of 20).
Best,
- Joe
···
On Dec 12, 2008, at 11:17 AM, Joe Strout wrote:
What's really weird is how inconsistent it is. Open the window one time, and some of the fields show the problem. Close it and open it again, and different ones (or sometimes none of them) show the problem.
We upgraded macholib today since that seemed to be necessary to get py2app to work successfully with MySQLdb.
But now, our (OS X) app is showing partial scrollbars in its TextCtrl fields. This is the case even when there isn't enough data in them to merit a scrollbar. Moreover, it persists even when we set the style to 0 -- which, from my reading of the docs, should make it a single-line EditField with no scrollbars.
What's really weird is how inconsistent it is. Open the window one time, and some of the fields show the problem. Close it and open it again, and different ones (or sometimes none of them) show the problem.
The problem never occurs on another machine, where we haven't upgraded macholib.
Any idea what's going on here, and how I can work around it?
This is the first time I've heard of anything like this. I'm not sure how macholib could have an effect like this because AFAIK it is only used by py2app to find the dependencies that need to be included in the bundle. I don't think it is used at runtime. Have you compared the contents of the app bundles in the two cases to see what is different?
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
Perhaps that's a red herring, then. I'll dig further.
Thanks,
- Joe
···
On Dec 12, 2008, at 11:48 AM, Robin Dunn wrote:
This is the first time I've heard of anything like this. I'm not sure how macholib could have an effect like this because AFAIK it is only used by py2app to find the dependencies that need to be included in the bundle. I don't think it is used at runtime. Have you compared the contents of the app bundles in the two cases to see what is different?