Programming Instruction

Does that in service mode switch on interrupts?

My 26 bit is rusty, bit doesn’t that zero all the flags? So turn on interrupts and put the processor in user mode…?

AFAIR:

TEQP pc,#0 ; Chages to user mode IFF (If and only If) we are not in user-mode, otherwise it should do nothing

While for the IRQ mode on, should it be something like:

TEQP pc,#2

???? – 26-bit memories are fading, sorry

Thanks Rick – it confirms what I was thinking.

The two irq’s are around the other way – setting the flag when they are disabled – don’t think the inst books made a point big point of it. :-(

By the way Rick using !Zap rick3 – is there a way of storing BASIC mode width to 120 – Auto width doesn’t seem to work.

Just added Wimp_PollIdle – I chose 50 for a value – is this value hit and miss?

The Laptop is sure running cooler. :-)

The delay you choose for Wimp_PollIdle should depend on how often your task really does need to see Idle events.

What are the colours numbers for SWI_Wimp_SetColour

Thanks

Pity the Paper and PDF versions of page numbers don’t match up :-(

For SWI Wimp_SetColour, the bottom nibble of the byte specifies which of the 16 Wimp colours you want to set for fg/bg

It was the colour numbers I was after.

Got around the problem by adding 1 to all the Wimp_SetColour one by one – ARM then BASIC till I came to the problem code.

Is there a easy way – of testing if a memory area is updatable – without upsetting BASIC?

Any info on Wimp Templates would be nice – my books seem to be missing this info – the Debugger loading templates seems to be poking into ‘Mother Earth’s :-)

It was the colour numbers I was after.

Thanks for that -
Something like.

0 White
1-3 Light greys
4-6 Darker greys
7 Black
8 Royal Blue
9. Yellow
10. Grass Green
11. Red
12. Pink
13. Dark Green
14. Brown
15. Light Blue

With ref to

SYS OS_Byte 129 &C3 &FF

What is it supposed to do?

There two choices – how do you tell them apart?

If WimpColour 12 is really pink and 14 brown on your screen, you should think very hard about colour-calibrating your monitor.

Looking on a phone screen was not so good.

You forget not everyone sees the same colour.

Loaded up !Paint 16colour sprite – hey they give the numbers!

Much better colours :-)

What do you think the colours should be?

There two choices – how do you tell them apart?

According to the Acorn PRM 1-870, OS_Byte 129 &C3 &FF would scan the keyboard waiting for internal key number 60 (“Enter” on numeric keypad) to be pressed.

R2 being &FF eliminates “read a key within time limit”
R1 being non-zero eliminates “read OS version identifier”
R1 being greater than &7F eliminates “scan for range of keys”

There appear to be two typos on the ROOL PRM page – the word “lowest” should be omitted from the description for R1, and the “Use” section should specify “a single key” rather than “a range of keys”. I am loath to make changes to PRM pages as it is possible I have – once again – got hold of the wrong end of the stick.

The standard colours are red and orange respectively.

@StuartP: That PRM entry looks a bit of copy/pasta from its friend: https://www.riscosopen.org/wiki/documentation/show/OS_Byte%20129%20(scan%20range)

You forget not everyone sees the same colour.

True, but pink ?

What do you think the colours should be?

According to DeskLib:

#define colour_WHITE        0
#define colour_GREY0        0
#define colour_GREY1        1
#define colour_GREY2        2
#define colour_GREY3        3
#define colour_GREY4        4
#define colour_GREY5        5
#define colour_GREY6        6
#define colour_GREY7        7
#define colour_BLACK        7
#define colour_DARK_BLUE    8
#define colour_YELLOW       9
#define colour_GREEN       10
#define colour_RED         11
#define colour_CREAM       12
#define colour_ARMY_GREEN  13
#define colour_ORANGE      14
#define colour_LIGHT_BLUE  15

I’d be inclined to also user dark green and cyan as alternatives to 13 and 15.

Put OS_Byte 129 in a task window in a repeat until false.

If r1 = 255 then P. r1 : end

Pressing num enter – doesn’t seem to work.

Does the OS wait for ever for a key to be pressed.

Note the Cream might gone off :-)

Ahh – &C3 num Enter doesn’t seem to work in a Task Window but using letter ‘L’ does.

Came across this -

Orr r0,pc,#0
Teqp PC,r0

I wonder what the author had in mind.

Zeroing flags – seems it would be in user mode.

Ref
Repeat
SYS"OS_Byte",129,0,0 TO ,R1

IF R1 = 255 THEN :ELSE PRINT R1
UNTIL FALSE

Seems to return ASCII numbers and 255 if no key pressed.

What is ASCII 27?

Doesn’t seem to be in the manuals – would it left over from RO2?

ASCII 27 is Escape isn’t it? If you do
PRINT GET
and then press Escape you’ll get 27

Thanks for that info – fits in with the code.

Lots of jumping around with 32bit code – 26bit certainly had its advantages.

I seem to have forgotten how to change keys behavior with VRPC.

Ie change the RO Break key to say the ‘*’ key on a Win Portable.

[Edit]

As it happens – the next key along works as the ‘Break’ key named as ‘Pause’

[Fn,Alt,Pause]

:-|

What’s the best way of getting a abort -

Mov pc,#0

Can someone move this thread to somewhere more suitable than Announce please?