On June 7, 2007 at 06:01, Springs said...
Ernie... I had 2 code pages at one point. Page one is
the one that the customer actually used with #s on it.
Those contained database codes and worked just fine.
I always have hidden pages that are just codes in stupid ugly 17x60 (or so) buttons made so I can get almost thirty commands to a page, then I alias every user button to those pages.
So I upped the duration on
the database codes on page one. NEVER MISSED AGAIN! So
I went back in and extended every database code to .15.
Then I tried referring to page one for the macros...
Works perfect.
Your method required only ten changes of delay lengths. Mine requires one, but it takes more time than yours because every macro has several "delay" commands aliased to the master delay button. I would now get even lazier and change your commands from, say
6... 0.15 second delay
to
6 "delay" button
Then changing the delay on every button requires only changing the length of the delay button, and your method of including a delay as part of the numeral shortens the time it takes to construct macros.
With that, I think we've just about beat the crap out of any programming time-saving that can be done here.
