User Feedback :: My numlock key does not work in DSL



I see. The problem must be with Kdrive. I don't understand why the project says it's using XFree86, then. And, I think I understand why installing the xfree86.dsl with accessx.dsl helped fix some errors; it probably installs a full enough xfree86 for control.

With an updated Debian Sarge, it can allow a 4.3.0 XFree86. And the MyDSLs allow a 4.3.0 XFree86. I see the relationship.
Geez... they're not errors. It's one little light, but the bleeping numlock still works.
In my boxes, I can't get the full functionality of the numlock.

I mean, well, xev is noticing the press of numlock. However, none of the effects of numlock are taking place. If numlock is off, then the numpad 4 is suppose to go left. For instance, I opened ted, and I kept getting a 4 instead of the cursor moving to the left.

Something is wrong. Oh, excuse me, functionalism doesn't apply to this community. I feel, uh (acts like Jeff Goldblum), an axiological issue of negativity has partaken, thee uhh, digital circuitry within this amazingly programmed operating system. I, uh, well if you would consider with me, don't think thee numberpad is functioning as its suppose to. Thus, the operating system was not well developed for various computers, or perhaps something, if you don't mind my enthymatic character, something is wrong.

Now, if I may, I have done some tests with the console and the various GUI projects that are symbiotic to the OS. However, I think the numlock doesn't live too well with the GUI environment. It has been unable to move to the left when pushing "4." However, inside of a console environment, it is enriched with nutrients and able to move the text cursor to the left. This has made me consider that perhaps the numlock works within the sense that xev reads it. Yet xev is a console application. This is not to say that it works well within the kdrive environment.
xev is a console app? Try running it in console then.. It's not.
Well, if I am mistaken, then I am mistaken. But I do know that opening a shell allows the usage of numlock. Programs, such as nano, allow me to move the cursor to the left. However, things, such as ted, did not allow me to do such a thing. It appears that anything beyond the shell does not seem to allow the full usage of numlock's properties. I researched this by looking through the kdrive/tinyx mailing list. It seems very apparent something is wrong with kdrive, so I'll let my views stand there.
Next Page...
original here.