Amiblitz 2 "invisible commands"

tolkien · 02 November 2016, 20:50

I have started to do some coding with amiblitz 2.44 and have a strange problem.
Some commands, like joyb() for example, are not displayed in the editor, are invisible!
Any idea why? With bb2 doesnt happend.

tolkien · 02 November 2016, 22:21

Solved! I have toyed with the tooltypes to use more colours and now is all ok!

Enviado desde mi ALE-L21 mediante Tapatalk

Daedalus · 03 November 2016, 10:27

Yes, AmiBlitz highlights some commands differently since they access the hardware directly. It's a good idea to keep them a different colour so you know when you're hitting the hardware, just so you can be aware of potential issues with multitasking or NG platforms.

tolkien · 03 November 2016, 11:46

Oh! So those commands hits the hardware? Are there a system friendly alternative?
Thanks for the tip.

Enviado desde mi ALE-L21 mediante Tapatalk

Daedalus · 03 November 2016, 13:06

There are usually system-friendly alternatives, but they're rarely as simple as the Blitz commands. Blitz commands highlighted in red (by default) hit the hardware, but if you're only intending the software to be used on a real Amiga, sometimes that's excusable, and it's perfectly fine if you're using Blitz mode since the OS is disabled anyway. Joyb() in particular is relatively harmless, it simply won't work when used on an NG system.

For the example Joyb(), the proper system-friendly alternative is to use gameport.device, or maybe lowlevel.library depending on what you're doing, though this is a bit more work. You'll need to read the system autodocs to learn how to use them - it's a bit more involved than Joyb() and might not be worth the effort, depending on what your intended target audience is.

Some information on gameport.device: http://amigadev.elowar.com/read/ADCD.../node04B9.html

tolkien · 03 November 2016, 13:44

Thanks daedalus. I'm used to code in C so understand what you say.
I dont care that those commands hits the metal. I only want to know what I am doing.
Thanks again mate.

Daedalus · 03 November 2016, 14:02

Ah, you're sorted so. Enjoy

02 November 2016, 20:50	#1
tolkien AmigaMan Join Date: Oct 2012 Location: Castro Urdiales/Spain Posts: 761	Amiblitz 2 "invisible commands" I have started to do some coding with amiblitz 2.44 and have a strange problem. Some commands, like joyb() for example, are not displayed in the editor, are invisible! Any idea why? With bb2 doesnt happend.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
"Voices8" 8 Channel Soundtracker "DemoSongI" song - "This is the Amiga with 8 Voices"	DemosongIHunter	request.Music	45	23 May 2022 20:07
"Screech!! v2.41" & "Screech!! [AGA] v2.51" - "HD install" --> "ADFs"	DamienD	request.Old Rare Games	45	15 June 2020 12:42
"Reminder "Lincs Amiga User Group aka "LAG" Meet Sat 5th of January 2013"	rockape	News	4	30 January 2013 00:06
CD32 Image-Name-Bug: "...(bla)[!].zip" -> "...(bla)[" / "...[test].zip" -> "...[tes"	cfTrio	support.WinUAE	8	18 December 2012 16:31
The "Invisible" Woody's World	Old Fool	support.Games	6	19 July 2007 18:07

02 November 2016, 22:21	#2
tolkien AmigaMan Join Date: Oct 2012 Location: Castro Urdiales/Spain Posts: 761	Solved! I have toyed with the tooltypes to use more colours and now is all ok! Enviado desde mi ALE-L21 mediante Tapatalk

03 November 2016, 10:27	#3
Daedalus Registered User Join Date: Jun 2009 Location: Dublin, then Glasgow Posts: 6,348	Yes, AmiBlitz highlights some commands differently since they access the hardware directly. It's a good idea to keep them a different colour so you know when you're hitting the hardware, just so you can be aware of potential issues with multitasking or NG platforms.

03 November 2016, 11:46	#4
tolkien AmigaMan Join Date: Oct 2012 Location: Castro Urdiales/Spain Posts: 761	Oh! So those commands hits the hardware? Are there a system friendly alternative? Thanks for the tip. Enviado desde mi ALE-L21 mediante Tapatalk

03 November 2016, 13:06	#5
Daedalus Registered User Join Date: Jun 2009 Location: Dublin, then Glasgow Posts: 6,348	There are usually system-friendly alternatives, but they're rarely as simple as the Blitz commands. Blitz commands highlighted in red (by default) hit the hardware, but if you're only intending the software to be used on a real Amiga, sometimes that's excusable, and it's perfectly fine if you're using Blitz mode since the OS is disabled anyway. Joyb() in particular is relatively harmless, it simply won't work when used on an NG system. For the example Joyb(), the proper system-friendly alternative is to use gameport.device, or maybe lowlevel.library depending on what you're doing, though this is a bit more work. You'll need to read the system autodocs to learn how to use them - it's a bit more involved than Joyb() and might not be worth the effort, depending on what your intended target audience is. Some information on gameport.device: http://amigadev.elowar.com/read/ADCD.../node04B9.html

03 November 2016, 13:44	#6
tolkien AmigaMan Join Date: Oct 2012 Location: Castro Urdiales/Spain Posts: 761	Thanks daedalus. I'm used to code in C so understand what you say. I dont care that those commands hits the metal. I only want to know what I am doing. Thanks again mate.

03 November 2016, 14:02	#7
Daedalus Registered User Join Date: Jun 2009 Location: Dublin, then Glasgow Posts: 6,348	Ah, you're sorted so. Enjoy

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)