Panner: Num Lock (on/off) problem

Shery Corgan

unread,

Jan 23, 2001, 11:05:28 AM1/23/01

to

Using SCO OS Unix 5.0.5 and Filepro 4.8
Using GUI -- Panner

I perform 90 % of my tasks using the SCO Panner.
The different windows need the num_lock on or off
depending on the window.

I would like to have the num_lock on or off to get
the calculator keys to work, but not both. I can not
find any documentation on this problem.

What happens now, by panner window, to get
numbers from the calculator_keys

window_1 on
window_2 off
window_3 on
window_4 off
window_5 on
window_6 on
window_7 on
window_8 on
window_9 on

Before accessing Filepro Main Menu (dpromenu)
I set the terminal type using a small script (on each
panner window) as follows.

term_script

setcolor hi_white blue
setcolor -r magenta gray
TERM=ansi;export TERM

Any thoughts or direction is appreciated, Shery

Jean-Pierre Radley

unread,

Jan 23, 2001, 11:48:07 AM1/23/01

to ScoMisc [c.u.s.m]

Shery Corgan propounded (on Tue, Jan 23, 2001 at 04:05:28PM +0000):

You shouldn't need to do that. I set the colors for my windows in my
.startxc file; If your filePro termcap file doesn't have scoansi in, it,
just add it to the asni entry.

# /u/jpr/.startxrc
#Oct 97: my ~/.Xdefaults file sets the following:
# font4 as default
# no menubar on start
# blinking cursor
# scrollBar
# mapchanAutomap False

# following file kills existing netscape and locks, relaunches netscape
/u/jpr/bin/ns

xclock -update 1 -hd magenta -hl magenta -geometry 100x100+0+1019 &

scoterm -fg cyan -bg black -n JPR -title jpr -geometry 80x47+0+0 &

scoterm -fg magenta -bg white -n JPR -title jpr -geometry 80x47+85+67 &

scoterm -fg yellow -bg blue -n JPR -title jpr -geometry 80x47+764+224 &

scoterm -fg blue -bg gray -n BOSS -title boss -geometry 80x47+1600+0 \
-e su - boss &

scoterm -fg green -bg black -n BOSS -title boss -geometry 80x47+1800+120 \
-e su - boss &

scoterm -fg black -bg white -n BOSS -title boss -geometry 80x47+2364+224 \
-e su - boss &

scoterm -fg white -bg red -n UUCP -title uucp -geometry 80x47+3200+0 \
-e su - uucp &

scoterm -fg red -bg cyan -n NEWS -title news -geometry 80x47+3964+224 \
-e su - news &

scoterm -fg red -bg gray -n APPL -title appl -geometry 80x47+4800+0 \
-e su - appl &

scoterm -fg blue -bg gray -n APPL -title appl -geometry 80x25+5564+126 \
-e su - appl &

scoterm -fg black -bg gray -n APPL -title appl -geometry 80x25+5564+665 \
-e su - appl &

win &

xv -root -rmode 5 -rbg "#107090" -quit /u/jpr/lib/valerie.jpeg &

exec pmwm

As for the LEDs settings, here's a short program; I run it from
/etc/rc.d, but you could of course fire it off differently for each
window.

/*
This code has been initially contributed by Jim Woolley of S Levy Inc. ;
it has been modified by Benoit Bruet (10032...@compuserve.com) to use
system console instead of standard input, to set any led combination passed
from command line, and to output previous settings.

Purpose :
=========

"setleds" allows anybody having read access to "/dev/console"
(usually superuser) to light up any combination of "Caps Locks", "Num Lock",
"Scroll Lock" LED's of the console keyboard. Its primary use is to have the
"Num Lock" LED lit as it is usual in PC/MS-DOS world. This should avoid some
trouble to system manager with users complaining to be unable to log at
console after a reboot when entering figures of their password at keyboard
keypad.

Instructions :
==============

"setleds" takes an optional argument. When present, this argument should
range from 0 to 7, and is obtained by OR-ing the following values :

1 to light "Scroll Lock",
2 to light "Num Lock",
4 to light "Caps Lock".

For instance, 7 would mean "all LED's on", 0 whould mean "all LED's off"
and 2 would mean only "Num Lock" LED on.

Whether it has an argument or not, "setleds" will return the previous
settings (0 at boot), which can be used for later restoration. If output is
unwanted, it should be redirected to /dev/null.

To have "Num Lock" LED lit at boot while discarding previous settings (0),
simply insert the following command as part of the boot process (for instance
in /etc/rc) :

setleds 2 >/dev/null

Warning :
=========

There is not kind of guarantee, either expressed or implied, with this
software, which is delivered on a "as is" basis only.

*/
# include <ctype.h>
# include <fcntl.h>
# include <stdio.h>
# include <sys/types.h>
# include <sys/ioctl.h>
# include <sys/vtkd.h>

int main(int argc,char *argv[])
{
int console,rc ;
char leds ;

rc = 1 ;
if(argc>1 && !isdigit(argv[1][0]))
{
fprintf(stderr,"usage: setleds [ 0-7 ] # OR-ed LEDs bits\n") ;
}
else
{
console = open("/dev/console",0) ;
if(console<0) perror("/dev/console") ;
else
{
if(ioctl(console,KDGETLED,&leds)<0) perror("ioctl") ;
else
{
printf("%d\n",leds) ;
if(argc>1)
{
if(ioctl(console,KDSETLED,atoi(argv[1])&7)<0) perror("ioctl") ;
else rc = 0 ;
}
else rc = 0 ;
}
}
}
return(rc) ;
}

--
JP

Shery Corgan

unread,

Jan 23, 2001, 12:23:10 PM1/23/01

to

Thanks for all of the detailed information. I will
certainly use it. I do not use scoansi because
the function keys do not work. For example:
on the dpromenu F10-Help (ansi) HELP-HELP (scoansi)

The information I have in the term_script is in y
.profile also. If I open a new panner window >> unix >> p
I get a black screen with white letters and scoansi
emulation (HELP-HELP instead of F10-HELP).

Thanks Shery

Jean-Pierre Radley

unread,

Jan 23, 2001, 12:48:08 PM1/23/01

to ScoMisc [c.u.s.m]

Shery Corgan propounded (on Tue, Jan 23, 2001 at 05:23:10PM +0000):

| Thanks for all of the detailed information. I will
| certainly use it. I do not use scoansi because
| the function keys do not work. For example:
| on the dpromenu F10-Help (ansi) HELP-HELP (scoansi)

| The information I have in the term_script is in y
| .profile also. If I open a new panner window >> unix >> p
| I get a black screen with white letters and scoansi
| emulation (HELP-HELP instead of F10-HELP).

Same cure.

If you do not want to edit /appl/fp/termcap, you could instead edit
/appl/fp/lib/config and insert
PFTERM=ansi

Actually, I use cansi, and have a full range of different colors for text
and errorboxes and messageboxes and fP-help. I've posted about this more
than once in the filePro mailing list.

--
JP

Shery Corgan

unread,

Jan 23, 2001, 1:18:58 PM1/23/01

to

Thanks a million -- I changed the filepro termcap
file. to [scoansi|ansi]. All works fine now, from the
brief test I gave it. Shery

Jean-Pierre Radley wrote:

I changed the filepro termcap file. to [scoansi|ansi].
All works fine now, from the brief test I gave it.

I thought I had looked in the file. I was interrupted a
few times. When you said it again I realized that I had not looked.
I should have double checked before I responded.

>
> | The information I have in the term_script is in y
> | .profile also. If I open a new panner window >> unix >> p
> | I get a black screen with white letters and scoansi
> | emulation (HELP-HELP instead of F10-HELP).
>
> Same cure.
>
> If you do not want to edit /appl/fp/termcap, you could instead edit
> /appl/fp/lib/config and insert
> PFTERM=ansi
>
> Actually, I use cansi, and have a full range of different colors for text
> and errorboxes and messageboxes and fP-help. I've posted about this more
> than once in the filePro mailing list.
>

I will make note and explore this when I have more time. I have
end_of_months and end_of_year work to do. I brought a totally
revamped A/R, receiving, e-scheduling for sales and installs
online one week before my Christmas vacation and did not
train the users quite enough. So I am interrupted quite often.
I documented everything for the end_user, but they would
rather ask than read through a manual.

Enough said, thanks a million for your assistance. It will cut
down on my frustration.

Shery

>
> --
> JP