Emulator r39 Released

svenvandevelde · Post by **svenvandevelde** » Wed Mar 30, 2022 5:16 pm

Bingo! Got it working now! So new interrupt vector at $0314 has value $E040.

svenvandevelde · Post by **svenvandevelde** » Wed Mar 30, 2022 5:37 pm

Any known issues with the mouse pointer? It seems the mouse pointer "get" api at $FFB6 is not working as expected.

Maybe I'm wrong, i baseline the mouse vectors to be returned at $22, which should be available to the user, right?

But it's not working. No mouse movement ...

ZeroByte · Post by **ZeroByte** » Wed Mar 30, 2022 5:40 pm

Has cc65 updated the repo yet to be R39 compliant?

rje · Post by **rje** » Wed Mar 30, 2022 5:48 pm

On 3/30/2022 at 12:40 PM, ZeroByte said:

Has cc65 updated the repo yet to be R39 compliant?

No. cc65's cputc(), cputs(), and cprintf() appear to be non-working for X16.r39. Text frame address change?

Michael Steil · Post by **Michael Steil** » Wed Mar 30, 2022 6:20 pm

On 3/30/2022 at 6:44 PM, svenvandevelde said:

And the interrupt return vector has changed also ?.

Where was that again ... address vector in $0314 ....

let me check ... E040?

The location of the default IRQ handler is not API and must not be relied on. It changes in every single revision of the ROM.

Read the current value in your code, and jump to it at the end.

Michael Steil · Post by **Michael Steil** » Wed Mar 30, 2022 6:23 pm

On 3/30/2022 at 7:37 PM, svenvandevelde said:

Any known issues with the mouse pointer? It seems the mouse pointer "get" api at $FFB6 is not working as expected.

$FF6B

svenvandevelde · Post by **svenvandevelde** » Wed Mar 30, 2022 7:14 pm

On 3/30/2022 at 8:23 PM, Michael Steil said:

$FF6B

Typo, you are correct, i meant to write $FF6B

So this code seems to be correct.

This is the API call fragment:

However, the zero pages $22, $23, $24, $25 stay 0, regardless if I move the mouse or not.

I"m sequently calling this CX16_MOUSE_GET continuously.

I've attached a demo prg with source code in asm.

cx16-mouse.prg cx16-mouse.c cx16-mouse.asm

desertfish · Post by **desertfish** » Wed Mar 30, 2022 10:07 pm

There's been a change in the mouse_config() API https://github.com/commanderx16/x16-docs/blob/master/Commander X16 Programmer's Reference Guide.md#function-name-mouse_config

However I think there's also a bug. Setting X and Y both to zero seem to reduce the 'screen size' to 0 by 0 blocks instead of keeping the 'current' resolution as the documentation now says.

I find that if you set them to 80 and 60 respectively, or perhaps follow the code snippet given in the docs, the mouse moves again.

Also there is a small error in the documentation, it still says "Communication registers: .A, .X" , this should be "Communication registers: .A, .X, .Y" now.

Michael Steil · Post by **Michael Steil** » Wed Mar 30, 2022 10:43 pm

On 3/31/2022 at 12:07 AM, desertfish said:

There's been a change in the mouse_config() API https://github.com/commanderx16/x16-docs/blob/master/Commander X16 Programmer's Reference Guide.md#function-name-mouse_config

However I think there's also a bug. Setting X and Y both to zero seem to reduce the 'screen size' to 0 by 0 blocks instead of keeping the 'current' resolution as the documentation now says.

I find that if you set them to 80 and 60 respectively, or perhaps follow the code snippet given in the docs, the mouse moves again.

0 does keep the current size config. It's just that if you never called mouse_config before, the current config is 0x0, which it will keep.

@svenvandevelde, you need to call mouse_config, like in the example in the docs.

Michael Steil · Post by **Michael Steil** » Wed Mar 30, 2022 10:44 pm

On 3/31/2022 at 12:07 AM, desertfish said:

Also there is a small error in the documentation, it still says "Communication registers: .A, .X" , this should be "Communication registers: .A, .X, .Y" now.

Pull request, please? ?