| Ultra Macros help please [message #338334] |
Fri, 24 February 2017 13:25  |
|
|
Originally posted by: SHartz40
I have an employee who often gets in a hurry and when using Appleworks 5.1, she hits oa-S instead of oa-crtl-S to save important files (which may save the file several layers deep in my hard drive and therefore essentially lose the file ) So her revisions to a large DB file are NOT saved to the desired (home) location. When I subsequently add the file from the desired (home) location again, her revisions are not in that copy of the file! A real problem....
I was trying to write a macro to disable her ability to save the file to a 'wrong' location. Here is my attempt, which results in a computer lockup. Can someone help?
<ba-K>:<all K=key if K=243 then bell bell msg 'No Katie. Its oa=ctrl-S. Remember' : else if K=147 then message 'Thats right Katie': else rpt>! Maybe use a 'sleep' command somehow? Where is my faulty logic ?
Or is there a way to 'disable' the oa-S command in Appleworks 5.1??
Thanks!
Steve
|
|
|
|
| Re: Ultra Macros help please [message #338350 is a reply to message #338334] |
Fri, 24 February 2017 14:33  |
Richard Thiebaud
Messages: 222
Registered: May 2013
Karma: 0
|
Senior Member |
|
|
On 02/24/2017 01:25 PM, SHartz40 wrote:
> I have an employee who often gets in a hurry and when using Appleworks 5.1, she hits oa-S instead of oa-crtl-S to save important files (which may save the file several layers deep in my hard drive and therefore essentially lose the file ) So her revisions to a large DB file are NOT saved to the desired (home) location. When I subsequently add the file from the desired (home) location again, her revisions are not in that copy of the file! A real problem....
> I was trying to write a macro to disable her ability to save the file to a 'wrong' location. Here is my attempt, which results in a computer lockup. Can someone help?
> <ba-K>:<all K=key if K=243 then bell bell msg 'No Katie. Its oa=ctrl-S. Remember' : else if K=147 then message 'Thats right Katie': else rpt>! Maybe use a 'sleep' command somehow? Where is my faulty logic ?
>
>
> Or is there a way to 'disable' the oa-S command in Appleworks 5.1??
>
> Thanks!
>
> Steve
>
Can't you remap the keyboard?
|
|
|
|
| Re: Ultra Macros help please [message #338351 is a reply to message #338334] |
Fri, 24 February 2017 15:15 |
Hugh Hood
Messages: 689
Registered: November 2012
Karma: 0
|
Senior Member |
|
|
Steve:
That macro results in a 'lockup' because you need an 'endif' to follow each
'if', unless the conditional 'if' proceeds to the end of the macro
statement.
Also, and more importantly, unless Katie is only saving the file when
prompted under macro direction (unlikely), you'll be stuck in the polling
loop when trying to do other work.
Fortunately, I'm fairly certain that you can solve this issue by disabling
the <OA-S> altogether (rather than just swapping with <OA-CTRL-S>, which can
also be done). This is the cleanest way, methinks.
I'll have a little time this weekend and will come up with a macro to poke
in the changes, as I don't have that info committed to memory.
You can then add it to the startup set so that it will run any time
AppleWorks is started. There will also be a corresponding macro that you
could use to restore normal behavior, should you so desire.
Oh, congratulations on continuing to use AppleWorks 5.1. I find it still to
be a wonderfully useful piece of software with which to do 'real' work, and
do it quickly.
Come to think of it, an 'init' might do the job more efficiently. We'll see.
Hugh Hood
in article e6ba36fc-0cc4-4a90-9a0f-973717f9c4f3@googlegroups.com, SHartz40
at SHartz40@yahoo.com wrote on 2/24/17 12:25 PM:
> I have an employee who often gets in a hurry and when using Appleworks 5.1,
> she hits oa-S instead of oa-crtl-S to save important files (which may save the
> file several layers deep in my hard drive and therefore essentially lose the
> file ) So her revisions to a large DB file are NOT saved to the desired
> (home) location. When I subsequently add the file from the desired (home)
> location again, her revisions are not in that copy of the file! A real
> problem....
> I was trying to write a macro to disable her ability to save the file to a
> 'wrong' location. Here is my attempt, which results in a computer lockup.
> Can someone help?
> <ba-K>:<all K=key if K=243 then bell bell msg 'No Katie. Its oa=ctrl-S.
> Remember' : else if K=147 then message 'Thats right Katie': else rpt>! Maybe
> use a 'sleep' command somehow? Where is my faulty logic ?
>
>
> Or is there a way to 'disable' the oa-S command in Appleworks 5.1??
>
> Thanks!
>
> Steve
|
|
|
|
|
|
| Re: Ultra Macros help please [message #338380 is a reply to message #338379] |
Fri, 24 February 2017 19:17 |
Hugh Hood
Messages: 689
Registered: November 2012
Karma: 0
|
Senior Member |
|
|
Steve,
OK. It turned out to be a bit simpler than I thought, so I just made a
couple of macros for you.
The first (SA-A) disables the <OA-S> 'save to current path' key.
The second (SA-B) enables the <OA-S> 'save to current path' key.
Change the macro names to something that suits you, add the macros to your
default set (and auto-run the 'disable' macro on start), and you should be
ready to turn it loose on your help.
Remember, this is a simple macro -- pressing <OA-S> will only beep as if it
were an invalid key. No 'error' message is presented.
I would make the 'enable' macro something that is unlikely to be pressed
accidentally, BTW.
If curious -- AppleWorks 'ReadKB' routine @ $115A is always on the lookout
for certain 'exit' keys. These include <ESC>, <OA-S> and <OA-CTRL-S>. The
macro bypasses the check for <OA-S>.
Let us know if that does (or does not) work for you.
Hugh Hood
------------------------------------------------------------ ----
Labels
..macrokillsave
Titles
\SA-A Disable <OA-S> key
\SA-B Enable <OA-S> key
\BA-L Launch Default Macros
Start
A:<all : pokeword $185C, $EAEA : // disable <OA-S> key
msg "<OA-S> Save File Key Disabled" :
> !
B:<all : pokeword $185C, $04F0 : // enable <OA-S> key
msg "<OA-S> Save File Key Enabled" :
> !
<BA-L>:<all: Launch "seg.um":>!
End
------------------------------------------------------------ ----
in article 3915f78f-45a6-45ee-8525-f3384c88aaa9@googlegroups.com, SHartz40
at SHartz40@yahoo.com wrote on 2/24/17 5:10 PM:
> Thanks guys, so much! I really appreciate it!
>
> Steve
|
|
|
|
|
|
|
|
| Re: Ultra Macros help please [message #338976 is a reply to message #338961] |
Thu, 09 March 2017 11:22 |
Hugh Hood
Messages: 689
Registered: November 2012
Karma: 0
|
Senior Member |
|
|
Steve:
My first thought is that the 'off' macro name you selected is already in
use. (The compiler will allow this and will NOT generate a duplicate
message, BTW).
For example, let's say you compile the following macro set, with both macros
named 'SA-A'.
When you execute SA-A, only the first instance will be processed. The second
one is ignored.
-------------------------------------------------------
Start
A:<all : print "first one" : >!
A:<all : print "second one" : >!
End
-------------------------------------------------------
I would also suggest that you de-compile the macro set you are using,
examine the commands (ON and OFF), and posting them here for me to take a
look at. Make sure you haven't used the same name earlier in the set, BTW.
I know when I wrote those (2) macros earlier, I tested them both and they
both did the job, so I'm sure it's something simple.
Hugh Hood
in article a3d85c86-974c-4692-807a-f7ab6e50cc66@googlegroups.com, SHartz40
at SHartz40@yahoo.com wrote on 3/8/17 10:51 PM:
> Hugh, it turns on just fine, but I can't get the 'off' to work...
|
|
|
|
Members
Search
Help
Register
Login
Home
