#Alt keys NOT working
28 messages in this thread
Philip –
I have a small problem with PPage 3.0 and it's one that has continued
from my previous version of PPage too.
Ever since upgrading to WB v2.04 the Alt hotkey combo's in PPage have
not worked or have worked incorrectly (bringing up the wrong requester). A
couple of examples includes;
Alt-W for the Wireframe Graphics toggle does nothing
Alt-T does not bring up the Tools requester
Alt-X is suppose to show the active box, but instead it brings up the
"Odd
Template Page Format" requester
Most of the other Alt combinations do not work at all. The only one
that does work is Alt-K for clone Active Box. All the items do work by
R-Mouse menu selection, but that's kind of expected.
I have been a long time user of PPage and was getting quite handy at
using all the shortcut keys to do what I want to do within the program.
But, like I said, ever since I upgraded to WB2.0 things have not worked in
PPage. I thought at first this was just a problem with the 2.1beta version
of PPage that I had, but now that I have v3.0 and the problem remains, I
don't know what to do.
I have not seen anyone else mention this problem – so I guess it has
something to do with my setup. But I don't know what??? I have check my
pref. settings and Icontrol but I really don't see how that is affecting
the program.
Do you or anyone have any ideas as to why these keys are not working for
me?? I really would like to get back to full productivity with PPage.
Thanks
– Roy Pahnke – Casper, Wyomin'
Roy,
I used to have a problem with some of the ALT key equivalents, and found it
to be my keymap. I was using the wrong one. Try changing it, or make sure
your using the most recent version. I'm not sure which one your using, but
I'm using WB2.0 usa0.
Chris
Chris
Thanks for the suggestion, I'll check it out tonight.
– Roy Pahnke – Casper, Wyomin'
Ok Chris –
I have check my keymap – things are set to USA0.
At first I check my Ram:env/sys/keyboard and it showed "usa" – ya just
usa, no 1,2, or 3. So I went through all the contortions required to reset
my env-archive and finally got things set up to USA0.
The only problem is that did not solved my Alt-Hotkey problem with
PPage.
Any other ideas?
– Roy Pahnke – Casper, Wyomin'
Roy:
For the heck of it, go in to the CX (commodities exchange) and disable or
kill anything that's running, then fire up PP and see if you get your hot
keys back.
Michael
…..on AutoPilot
Sounds like an idea Mike –
I'll try shuting down all commodities.
And Chris;
If Michael's idea doesn't work, I'll go through the Startup
line-by-line.
I'll keep ya posted guys. Thanks
– Roy Pahnke – Casper, Wyomin'
Mike –
I good idea, tryed it with no luck.
See my message to Chris.
– Roy Pahnke – Casper, Wyomin'
Roy, OK its not the keymap, eh? Did you try any others? Well, then I'd try
a Ctrl D after the startup-sequence starts and stop its execution, then
manually do the PPage required assigns in the shell and run the program
before anything else gets started. Then try the keyboard sequences again.
If they should then work, go through the execution of your startup-sequence
but don't load the Workbench. run PPage again from the shell. If the Kybd
equivalents still work, loadWB and try it again. What little programs are
you using that might interfere or takeover certain kybd strokes?
This sounds like a royal pain, but I'll tell you how I solved a problem
with Snap1.6 crashing the machine when I tried to snap a graphic object. I
did just what I described to you above. I typed one line of the sequence at
a time in the shell, and kept running and quitting snap, cutting graphics
and trying to save, looking for the line that caused the save requester to
jam. I ended up having to put it before anything started in my user-startup
and it all works fine now. Something happened after the workbench loaded
but Snap still wanted to be first.
Let me know if anything works,
Chris
Chris – (And Mike)
OK, here's what I did and it's not good news.
I first Ctrl-D at the very start of the startup-sequence and the ran
PPage. You were right, PPage ran perfectly and the Alt keys worked. Ok, I
figure that I would just run my Startup-sequence and not my user-startup
and see what happened. So I edited the SS file to end before loading WB or
my U-Startup.
Now, my SS file is pretty much original Commodore. Right from the start
I took their advice and did all my extra assign's and run's of extra
programs from my U-Startup. So here, I figured the problem would probably
be in my U-Startup file. But, it's not! I let the SS file run and then
loaded PPage and sure enough the Alt keys stopped working. Now I'm dead in
the water, cause I can't figure out what it is in this file that is causing
the problem. I tried running the SS file without IPREFS – but that's not
it. Otherwise the SS file doesn't really do a whole lot except set up the
ENV-Arc in RAM:
I can upload the SS file here in the message base, but really it's just
C='s file and I don't know why it should be causing a problem.
Again – any ideas, guys
– Roy Pahnke – Casper, Wyomin'
Roy,
It sounds to me like it boils back down to the keymap. I'd check that
Envarc: file keyboards. Check it in here :Prefs/env-archive/sys/keyboard. I
just checked mine and it says usa not usa0. I believe usa is in the ROM not
on the disk file. So maybe just edit the file its only text, but you should
be able to change it with WB.
Chris
Chris,
I think you are right, but I went through this the other night. Just
checked again my :Prefs/env-archive/sys/keyboard reads USA0, therefore my
RAM:env/sys/keyboard reads USA0. Before I changed things two night ago my
:Prefs…/Keyboard also read just USA. I changed something there but it
made no difference.
Let me ask you this – How did you 'step through' your startup-sequence
and run one line at a time. Is there away to do that in a shell or did you
have some sort of DeBug utility that would help you. Otherwise did you
just type in each line one at a time.
Gosh – maybe Don C. will see this thread and jump in here. Somebody
who really knows the C= startup inside and out.
For now I'm off to mess with the Keymap somemore – maybe I'll try
USA3….. 4 or 5 😉
– Roy Pahnke – Casper, Wyomin'
Roy,
I was wrong the first time when I told you I was using USA0, that was
because I looked in my keymaps and only saw usa0, when I checked the
keyboard env:sys/keyboard it was usa. Apparently usa is in ROM.
I don't know how to make the Startup-sequence step by itself, I typed
one command in at a time and checked the result.
I don't think there is a usa3 or 4 or 5.
Let me know if you figure it out,
Chris
usa3 = californianese
usa4 = bostonese
usa5 = brooklynese
<g>
// Michael
\X/ …on AutoPilot
Greay, it's going to map keys around so we talk in accents.
I had ones set up to map W to V, for scandinavian, and R to W for lisps….
eixt
Michael,
>>>usa5 = brooklynese <<<<
Sorry Michael, you got that one wrong. Brooklynese would be "usaTree".
Jonathan
(…a former Brooklyn native. Wanna make sumthin' outta it?)
– via Whap!
"usaTREE" is the alias.
Michael
<born in Brooklyn>
Chris & Mike –
OK – Problem solved!! Chris you were right – it was in the setting of
the keymap. But, "USA0" – is the WRONG keymap to use, the one that works is
just plain "USA"!
Before I go further, I have to proclaim thanks to Casper's resident GURU
Tom Miller! (He made me promise I would give him credit. He also has a CIS
account and now that he knows about this thread, he just may check that I'm
givin' credit where credit is do 🙂 Tom and I used to be partners in our
Amiga Computer store here is Casper and now that the store is closed we
still remain friends. I called him this morning to ask if he had a
solution to the problem. He first suggested I try a Alt-P within a
shell/CLI window. That should give one the Paragraph symbol. Mine didn't –
it just gave me a p. This was a lot easier test than having to load PPage
from the shell all the time. Anyway, Tom's Ram:env/sys/keyboard showed an
"USA" so I switched back to that one. Sure enough my ALT-p worked
proberly.
OK – now why did I have to change is back? When I started this thread
my Ram:env/sys/keyboard also said UAS, but unbekownst (sp?) to me was the
little line I (underline I) had put in my C= Startup-sequence that was
setting the keymap back to USA0. So even though my env/sys/keyboard in
both RAM: and SYS: was set to read USA, I was setting it back to USA0. Now
when Chris suggested that he was using USA0 (I think perhaps you really
weren't, Chris. You said the other night that your sys/keyboard read just
USA ) I went ahead and made a permantent change to USA0 in my keyboard file
(in reality though, I had been using that one all along, so I actually made
no change). Is this making sense to yous guys? 😉
So now I have made the switch back to USA, taken the silly setmap line
out of the startup-sequence, and rebuilt C='s startup-code that set the map
to the env/sys/keyboard file. I guess this whole mess started for me back
when I first switch to WB2.04. At that time the dumb startup kept wanting
to run that
[ MORE ]
[ continuation ]
'Pickmap' program that is on C='s WB disk. I couldn't figure out how to
avoid that request to pick a keymap at every boot up, so I inserted the
setmap command. Should never had done that and I have since learned about
the SYS: and RAM: Env-Archive files.
Thanks guys for the help. Chris I hope you didn't change your keymap to
USA0. And now it's on to other problems.
P.S – You know guys, I'm a real Lurker around here. I'm on everyday, read
alot of messages in AmigaTech, Vendore,and User (Hardly ever get into the
Arts). And with the recent discussions about lack of activity on these
boards this summer, I just might shake myself out of the Lurker mode and
back into taking a more active and responsive participation in these
forums. Having been a member of these forums for almost 10 years – it does
tend to run in cycles with me, but you two are good participators (sp?) and
I appreciate that yous guys are the one that pitch in to help me out.
Taking a cue for you then – I'll speak up more often and return the favor
to someone else in need of help.
Thanks guys-
"Be readin' ya"
(c) Roy Pahnke – 1985 🙂 –
Roy,
You have been an excellent participant here over the years, and we've
missed your input. We'll be glad to have you participate more often.
Sure Betty –
Ya, I've kind of been in just a quiet mood for awhile.
I think it was the place I was livin' in. It was a cramped little
apartment with a ceiling only about 6'5". The TV and stereo was in
another room and my computer table was swamped to overflowing with STUFF!.
Now, I have bought another home and I'm going to be very comfortable here.
Alot more room and a computer desk the is much better organized. So I
think it's a state of mind that has been effected by my environment.
Anyway, thank you Betty
"Be readin' ya"
(c) Roy Pahnke – 1985 🙂
Roy:
Great mystery story! I'm gald you figured it out. It's amazing somethimes
how hard it is to solve those little problems that you KNOW are simple.
I miss having you aorund (participating) so I hope you can be more active.
How's the restaurant business been for you this summer?
// Michael
\X/ …on AutoPilot
Mike –
Ya, something I did, but didn't think I did and didn't see that I did it
??)
Ye olde' Pizza Hut has been busy this summer, plus movin' to a new house
and settin' up said house, has kind of kept me goin' this summer. I can't
really comprehened that is already Aug. Oh well – it happens every summer
– doesn't it.
"Be readin' ya"
(c) Roy Pahnke – 1985 🙂
"…can't really comprehened that is already Aug."
No kidding!! I can't believe how fast this one slipped by. We had record
breaking rain in July, so it was kinda like we missed out on an entire
month of summer 🙁
// Michael
\X/ …on AutoPilot
Go in to Prefs/ICONTROL and check to see what Alt key assignmnets are made
there… and adjust them to something that doesn't conflict with PP.
Let me know if this works!
// Michael
\X/ …on AutoPilot
Michael –
I thought about that one a long time ago (under PPage 2.1 – after I
first installed WB2.04) and I really don't use any of the hot keys under
IControl. My control keys for screen front etc. are, of course, set to
R-Amiga, but the area labled for "Mouse Screen Drag" are NOT checked at
all. I don't use it.
I think Chris is right and it has to be in the SetMap – although I think
I'm using USA0, but I'm going to check again.
Thanks, though, for the thought – your suggestions are helpful and are
appreciated.
– Roy Pahnke – Casper, Wyomin'
good luck… let me know how you solve it.
// Michael
\X/ …on AutoPilot
Roy,
I had something in my WBStartup drawer that was stealing a hot-key from
ProPage. Don't remember what it was though. But I changed its key to be
something I never use and got back the key for ProPage.
It seems the commodities see keystrokes before anything else.
Malcolm