Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Mia]

Ok, I've done the work refactoring and found that these libraries are incomplete  and don't have the features needed for my App the way it is, I'll have to change the design.

I've got 2 versions done for each of the extensions I tested over the past 2 days.
 
I found that:

The Intuition Extension doesn't have a Mouse Zone and cannot report back mouse keys at all, it has a "bit" format in the documentation but nothing, it doesn't work, Mouse X/Y is fine. The library is also unstable and will crash a lot, expecially on loops testing the for MouseKey/X/Y/Scancodes - It has a better system to markup the Gui as you can program the menu's etc. but it was not a joy to build to a big thing with it. There is no Xor Screen Copy

The Gui Extension has the features needed but it's "events" system caused me problems, specifically mouse events again - you get a "-11" event for both a mouse down and then again on a mouse up, but not everytime and I'm using "Gui Wait" to wait for these events in a system friendly way - if you try to use this in your logic it will get locked up as the results are inconsitent - it would require too much debugging to get my gadgets working - normal proportional sliders would be ok, but not powerfull enough for what I need. And when opening hires screens sometimes there is jitter on the audio  - the use of GadToolsBox to design the Gui is a good idea, but it's the older version and too "locked in"/difficult to change programatically and I had some difficulty with blanked out menu's as the text and background got stuck the same colour. I fixed it at some point then the problem came back. Basically it took too long and then  became unstable. And it doesn't have an Xor Screen Copy command, there is a way around that using an AMOS screen as well, but I've decided to stop working with them for the App in it's current design - I probably have to move away from the custom gadgets and use windows not screens...

I would use the Gui Extension again for something but I would not advise trying to develop a game using it, The Gui Extension is stable, but quirky with the mouse and the events system, but the Intuition Extension proved itself to be too buggy to use.

[bruceuncle]

Hi Mia, If you haven't already found them, there's a package I put together a while back with "Resource" disassemblies of all the collected AMOS Extensions, and including Resource itself.  It's in this thread.  They're in Resource's own *.rs format as that's the most flexible for any further work.  Resource symbol libraries for AMOS xxx(a5) and most of the AMOS structures are also included.  As usual, the Read Me will tell you more than I can reasonably post here     They're intended as 'first cut'.  Most common bug is a few that use absolute addressing  ...  Anyway, let me know if they're any use and for any advice on using Resource.

[Mia]

Hi Bruce,

Thank you so much for pointing me to the thread - perfect timing, I have been meaning to take a close look at what you have done with 2.1 I'm starting to get really interested -I have downloaded it but not tried it yet and I will need a few more weeks before I comment - i need to catch up with you guys first and I don't want to annoy with duplicate questions etc.

The project I'm working on has convinced me to continue it with AMOS - I do have 68K skills but now only for debuging and tweaks - I do understand the disassembly process and I'm pretty amazed at what you are up to reverse engineering, and from what I've seen I am confident in what you doing. I need to review all the docs and stuff i'll be in a better position to comment - There's quite a bit to learn...

my new stuff is working with interrupts on the low level, but it's quite difficuly as aliens keep hacking my amos 

[Mia]

yeh - respect to you bro!

I can see my modifcation for UDP Datagrams will work with GUI2 as well...

thank you for your clear documentation it was easy to follow, this might be even more fun ;-) thank you so much.

obviously I will test this lol, havn't re-assembled it, but at line 8265 from the .asm I can see to change MOVEQ #1,D1 to MOVEQ #2,D1 - and UDP sockets will kick in - as i said I can debug and tweak  68k 

Code: [Select]

MOVEQ #2,D0
MOVEQ #1,D1
MOVEQ #0,D2
JSR (-$1E,A6)
MOVE.L D0,D2
TST.L D0
BLT.B lbC004D18


[Mia]

And to comment again on the thread: I kept on working with GUI Extension and it is VERY VERY good once you grasp the events system, it works without problems now - but currently not when compiled, but you've convinced me even more to continue with it as it's probably my fault not the exension, and I can see the source code now :-) - just not sure yet, and i've been working on the amos native version more. I have not experimented with the Intuition extension any more as the crashes are morale destroying, even though I think the problem is clipping and graphics library related and I could debug a bit more, I'm going to focus on the GUI extension as it does what I need very well...