Tzafrir Cohen
Tue, 03 Jul 2001 03:11:57 -0700
On Tue, 3 Jul 2001, Nadav Har'El wrote: > On Tue, Jul 03, 2001, Tzafrir Cohen wrote about "Re: 'r2l' continuation": > > And we must all keep in mind that biditext is inherently limited, because > > it works at avery low level, and the application is not aware of it by > > any means. Therefore it cannot be easily cotrolled from within the app. > > So there's also a problem that it cannot really have its own event loop... > I'm not sure how to get around this problem... Anyway, polling X-Windows > properties is still better (I think) than polling files, especially for > someone whose applications run on different machines, but display on one > display. You are confusing two things here: biditext.so needs not poll. It needs to only check once. In fact, how does a check of an X property compare to a stat() of a file ? Is it not too costly to perform such a check every time a string is drawn? GUI clients, who may want to report the status, may need to poll, or otherwise be notofied on changes. One other thing: I think that a global (per-display) property is not a good idea, because you may want two clients where one has biditext diabled and one has it enabled. A top-level-window property may be user-frinedly. The problem is how to get biditext to find the top-level window it is running in. Assuming that a process holds only one top-level window, and that this window does not change in the lifetime of the process, the following might work: http://www.mail-archive.com/lin-club%40vipe.technion.ac.il/msg00297.html But I haven't got around to even start implementing it :( -- Tzafrir Cohen mailto:[EMAIL PROTECTED] http://www.technion.ac.il/~tzafrir