Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Freezes coz of newly added key composition support #339

Closed
SDLBugzilla opened this issue Feb 10, 2021 · 0 comments
Closed

Freezes coz of newly added key composition support #339

SDLBugzilla opened this issue Feb 10, 2021 · 0 comments
Labels
duplicate This issue or pull request already exists

Comments

@SDLBugzilla
Copy link
Collaborator

This bug report was migrated from our old Bugzilla tracker.

Reported in version: 1.2.12
Reported for operating system, platform: Mac OS X (All), PowerPC

Comments on the original bug report:

On 2007-08-18 23:12:46 +0000, manutoo wrote:

I reported freezes on the newsgroup here : http://article.gmane.org/gmane.comp.lib.sdl/34324

console.log contains :
"2007-08-18 08:48:22.368 Tennis Elbow 2006[277] Exception raised during posting
of notification. Ignored. exception: *** -[NSLayoutManager
glyphRangeForTextContainer:]: given container does not appear in the list of
containers for this NSLayoutManager."

someone said he had the same trouble but with SDL 1.3 and pointed out this revision :
http://libsdl.org/cgi/viewvc.cgi?view=rev&revision=3217

Then, I commented out these lines :
1- [field_edit interpretKeyEvents:[NSArray arrayWithObject:event]];
2- field_edit = [[NSTextView alloc] initWithFrame:r];

and now, the freezes seem to be gone ! (at least on my system, I still need to get confirmation from my users).

On 2007-08-19 05:46:29 +0000, manutoo wrote:

One user just reported he didn't have freeze anymore and it also corrected the slowness he was experiencing on his G4 dual, OSX 10.4, GeForce4 MX AGP 64MB .

On 2007-08-20 13:58:02 +0000, Will Glynn wrote:

Seconded. I see occasional-to-frequent crashes in an entirely distinct code base giving the same message on the console, though I haven't tried that workaround yet. I found this bug report via the below discussion as indexed by Google.

On 2007-08-20 23:52:03 +0000, Sam Lantinga wrote:

*** This bug has been marked as a duplicate of bug 471 ***

@SDLBugzilla SDLBugzilla added bug duplicate This issue or pull request already exists labels Feb 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

1 participant