Indeed are you using Carbon or Cocoa, Carbon IMHO is really getting left behind. Yosemite introduced several bugs for our carbon based applications that were not addressed before the release of the GM.
Yes, it’s a Carbon app at its core, and all new functionality is being added as part of a set of Cocoa dylibs. There is a Cocoa migration effort in place, but those things take time.
I was wondering if anyone else had seen this issue, and if so, how they worked around it.
I have not had the same issue (I also have a Carbon application which I had added in Cocoa functionality), however on Yosemite I have received error reports a plenty from various Cocoa functions as well as other weird graphical glitches (heck I’m even getting graphical glitches in pure Cocoa based apps).
I read this morning about many people having unsolvable Wi-Fi issues in Yosemite and the solution seems to be reverting back to Mavericks.
Out of 12 apps, only 2 have no issue on Yosemite. One of the two is even a Carbon application.
Just a thought. Would it be possible that a TextArea did not exhibit the issue ? If so, maybe you can use one instead of the TextField. That will not change the imperious need to go Cocoa, but it may be a temporary fix.
@Michel Bujardet I doubt it will change behaviour since both TextArea and TextField inherit from TextEdit. And these really are intended as one-line text fields.
The only ones who know for sure what the differences are between TextField and TextArea are the framework implementors; maybe they can chime in?
@Joe Ranieri thanks, that’s what I would suspect. We also have a mixture of TextFields and TextAreas in some windows, and when typing stops working, neither of those respond to typing.