exxos blog - random goings on

[exxos]

The joy of programming...

:D

Still hate programming :lol:

[HigashiJun]

The joy of programming...

:D

Still hate programming :lol:

Then this one suits you better:

Prog2.jpg

;)

[exxos]

Then this one suits you better:

:bravo: :lolbig:

[exxos]

So starting to patch back in the test routines. Of the time text is misaligned (one character to the right to many) and other times like in the example below, I run the first test and it put the text in the wrong boxes and even included to 0% scores.. bonkers.

Capture.PNG

Now need to work out why those routines are now misbehaving :roll:

[exxos]

Got another mystery now it seems :roll:

I have it outputting a bit of debug information in the main event loop.

Code: Select all

MAINID	,our_aeshandle	,mess(3)	,e
 0             1             0             0 

mess(3) is what evnt_multi is returning when I click on the main window or a test. It does not match the AES handle of the window.

Then if I move the window starts to behave correctly..

Code: Select all

MAINID	,our_aeshandle	,mess(3)	,e
 0             1             1             16 

BUT.

The window move functions do this, which doesn't match to start with. So should not be able to even move the window in the first place :pullhair:

Code: Select all

if mess(3)=our_aeshandle

So for whatever reason the AES does not see any activity on the window whatsoever other than the title bar clicks :shrug:

EDIT:

I could just remove the handle check, then the mouse clicks register as expected. But I don't think it is really safe to do this with key presses as well. As it would be capturing "ANY" key presses the system sees and GB7 would process them keypresses even though it is not in focus. In actual fact I think the original GB6 I did probably suffer from that problem :shrug:

EDIT2:

Just tried my multitasking environment and pressing "A" selects stuff on the desktop and doesn't trigger GB6 events. Maybe you're not supposed to check the handle.. Will have to see what other program examples do..

[exxos]

So it looks like the handle is only checked when clicking the window for moving it for example.

This comes from the AESDEMO.BAS examples. I assume this is the correct method and I am not supposed to be checking the handle for events inside the window.. Bizarre...

Code: Select all

 IF mes_type>=WM_TOPPED AND mes_type<=WM_MOVED THEN
	IF mess(3)<>our_aeshandle THEN EXIT SUB	'its not our window
 END IF
 SELECT CASE mes_type
 CASE MN_SELECTED:
	' its a menu

[exxos]

Well I found why the main window figures were not updating correctly :lol: :roll:

Capture.PNG

[exxos]

Puzzling over this now. As GB must be some internal number as it seems to vary.

Code: Select all

MAX_PROGS=PEEKW(PEEKL(GB+4)+2

The accompanying code is basically..

Code: Select all

IF max_progs>1 THEN
	IF GETCOOKIE("MagX",dum&) THEN cookie_tasking$="MagiC Multitasking O/S" : EXIT FUNCTION
	IF GETCOOKIE("Gnva",dum&) THEN cookie_tasking$="Geneva Multitasking O/S" : EXIT FUNCTION
	IF GETCOOKIE("MINT",dum&) THEN cookie_tasking$="MultiTOS O/S (MINT)" : EXIT FUNCTION
ELSE
	cookie_tasking$="Standard TOS Single tasking"
END IF

So in TOS206 it outputs "1" in XaAES it outputs "-1" so .... :WTF:

[stephen_usher]

-1 would usually denote an error condition.

[exxos]

-1 would usually denote an error condition.

ah yep. So no idea about why that errors then. I will just remove that function and not bother with it.