Smart questions
Smart answers
Smart people
INTELLIGENT WORK FORUMS
FOR COMPUTER PROFESSIONALS

Member Login

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips now!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

Join Tek-Tips
*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

LINK TO THIS FORUM!

Add Stickiness To Your Site By Linking To This Professionally Managed Technical Forum.
Just copy and paste the
code below into your site.

Partner With Us!

"Best Of Breed" Forums Add Stickiness To Your Site
Partner Button
(Download This Button Today!)

Feedback

"...I love the structure of the site. You start at the top, and drill down to what you want. Maybe I've been using Unix too long... :-) "

Geography

Where in the world do Tek-Tips members come from?
fdservices (IS/IT--Management)
17 May 12 7:44
Having some problems with the state of the numlock key with my tcltk programmes. Problem is I am running Linux (numlock enabled) and windows in Virtualbox (numlock enabled) but when I open my tcltk programme I find that the numlock is disabled.

How can I tell the state of the numlock key and then toggle it if necessary, from within my code?

Thanks

Andrew
Bong (Programmer)
17 May 12 10:15
In Windows, at least, you need to do it in Assembler:
check here

_________________
Bob Rashkin

fdservices (IS/IT--Management)
17 May 12 10:24
Problem is I am running Linux
Bong (Programmer)
17 May 12 11:34
Well, there is a way of doing through KDE but with other desktops it looks like you need to use 3rd party software (numlockx). see here

_________________
Bob Rashkin

fdservices (IS/IT--Management)
3 Jul 12 4:00
Counter intuitively it seems that if I add:

catch {exec numlockx off}

then it solves the problem, but then I have to turn it back on when I leave the programme. Weird.

Here is my solution:
wm protocol . WM_DELETE_WINDOW {catch {exec numlockx on}
exit}
# set numlock off so that we can use it
bind . <Enter> {catch {exec numlockx off}}
bind . <Leave> {catch {exec numlockx on}}
bind . <FocusIn> {catch {exec numlockx off}}
bind . <FocusOut> {catch {exec numlockx on}}
catch {exec numlockx off}

Thanks for the help

Andrew

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members!

Back To Forum

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close