 |
| |
|
| |
|
|
Ari Rahikkala
|
 |
Unreported loss of streaming in atomic read operation
Oct 1999
time: 07:17
|
|
quote:
Originally posted by Asher
Just what universal text input widgets exist?
You do realize that games do not use the OS input widgets, right? You do realize that XUL-based apps (Firefox, Thunderbird, Mozilla) do not use the OS input widgets? you do realize that Java-based apps do not use the OS input widgets (SWT being the exception)? |
Allright, you got me there. Actually I did believe that XUL back-ends on the native widgets of the platform it's running on... but I couldn't find any conclusive information about that by either poking around in the source or Googling. Some say that XUL draws with native widgets, some say it doesn't, some say it draws only some stuff with native widgets but not everything. The source has a lot of references to things like gtk_entry_new (GTK+ function for creating a textbox - I used that as an example to look for since GTK+ is the only interface toolkit I've ever coded anything on) but most of them are in the installer... and I couldn't find any code that calls the functions in gfx/src/gtk/gtk2drawing.c, the file using native (well, "native") widgets that looked the most promising to me.
quote:
To have it globally like Aggie described would require an inefficient implementation to intercept keystrokes and put them in a buffer, then spellcheck them. |
Yes, it would be inefficient, but you'd be hard-pressed to actually notice the effect. Really, typing is *slow* - the last place where I remember actually seeing the screen lag behind keyboard input was in the DOS window of a WinXP laptop  . In the environment I'm using, a keypress goes through the X server to an application and is returned to the X server as a graphical glyph. That seems to work quite well for me. Some Slashdot trolls who don't understand that your $modern_processor is there to be *used* might disagree...
quote:
Further, how does this even WORK on non-standard input boxes? Do you randomly draw red lines where you THINK the text is? |
This is a good point, and... it made me think about some further problems with the daemon approach. Never mind the fact that creating any sort of a usable interface for it would be impossible (I'd hate a computer that beeps at me when I misspell something (even though I rarely do - I learned English by writing it, not speaking it  )), it'd also have problems with localisation (how do you know what language the user is supposed to be using?), with figuring out any sort of movement in textboxes other than going left or right one character at a time (where do you hop to if the user presses the up arrow in a textbox whose width you don't know? How do you *know* it's a textbox to begin with?).
Because of all of these reasons... I'm starting to doubt whether anyone really uses the daemon-intercepting-keypresses approach. If someone does, well, it's pretty likely to be just an ugly kluge that breaks when you actually try to do something with your computer. Very likely the sort of thing that breaks so quickly that some users would think it doesn't do anything useful at all...
|
|
| |
|
| |
|
| |
All times are GMT. The time now is 05:17.
Apolyton Time is 00:17. |
top of page
|
| archivepost |
|
Forum Rules:
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
|
HTML code is ON
vB code is ON
Smilies are ON
[IMG] code is ON
|
|
|
|
|
|
08-12-2004 00:38
That's what you are. You're the one talking about a plot of IBM to buy Apple's PC business so it can drive Microsoft out of business 
.
|