Subject:
|
Re: SetClock defined
|
Newsgroups:
|
lugnet.robotics.rcx.nqc
|
Date:
|
Wed, 17 Mar 1999 03:25:55 GMT
|
Viewed:
|
2456 times
|
| |
|
|
Mark Overmars already forwarded your SetClock definition to me, so it will
be added to 1.3, although I'm considering naming it SetWatch() for
consistiency with the nqc -watch option and the spirit.ocx call.
Dave
In article <36EE10DF.51EF1AA4@pacbell.net-nospam>, David Chen
<nospam-dcchen@pacbell.net-nospam> wrote:
> I noticed that the byte code command to implement the
> SetClock(hrs,min) wasn't implemented in the nqc.h file. Here it is,
> rather simple really but I find it useful as a way for the RCX to
> communicate debugging info while running.
>
> Example, when a Task1 is running, it can display 01:01 and change the
> minutes based on what state it is currently in or what it is
> doing. Another task can display 02:xx message as it desires when it
> is executing. Handy for me when debugging a program with many
> states, less obnoxious than making noises.
>
> The rcx.h definition is: #define SetClock(h, m) asm { 0x22,(h), (m) }
>
> If you use RcxCC 2.2, you can set a Template for this with the following
> Template definition: SetClock("hours","minutes");\=
>
> BTW, Great job on version 1.2 Dave!! Thanks for all your hard work.
>
> Hope you all find this useful,
> Regards,
> Dave Chen.
--
reply to: dbaum at enteract dot com
|
|
Message is in Reply To:
 | | SetClock defined
|
| I noticed that the byte code command to implement the SetClock(hrs,min) wasn't implemented in the nqc.h file. Here it is, rather simple really but I find it useful as a way for the RCX to communicate debugging info while running. Example, when a (...) (26 years ago, 16-Mar-99, to lugnet.robotics.rcx.nqc)
|
2 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
