14 December 2018, 22:48 | #1 |
Hardware Designer
Join Date: Aug 2018
Location: Bialystok/Poland
Age: 50
Posts: 178
|
GfxFree() surprise
I've written following code:
Code:
struct MonitorSpec *msp; if (msp = (struct MonitorSpec*)GfxNew(MONITOR_SPEC_TYPE)) { GfxFree((struct ExtendedNode*)msp); } My guess is they simply forgot to add the later two moving from KS 2 to 3. It probably went unnoticed because usually monitor spec structures are never freed. I wonder if it has been fixed in KS 3.1. |
15 December 2018, 04:46 | #2 |
Coder/webmaster/gamer
Join Date: Oct 2001
Location: Canberra/Australia
Posts: 2,630
|
Yes, this was fixed for KS3.1.
|
26 October 2019, 08:04 | #3 |
Registered User
Join Date: Sep 2018
Location: Rome / Italy
Posts: 22
|
I have almost the same problem with GfxNew while attempting to allocate a VIEWPORT_EXTRA_TYPE structure. I get a recoverable alert 0200 000C.
I am using KS 39.106 on WinUAE I am going to check if any patch is available. I wonder if it is safe to simply allocate the ViewPortExtra structure by code. I suppose it could work safe now but pheraps it could be incompatible with possible changes in future versions of AmigaOS... |
26 October 2019, 10:05 | #4 | |
Registered User
Join Date: Jan 2019
Location: Germany
Posts: 3,215
|
Quote:
Note, however, that GfxNew() and viewport functions are only supposed to be used by intuition, for building screens, namely. |
|
27 October 2019, 16:56 | #5 |
Registered User
Join Date: Sep 2018
Location: Rome / Italy
Posts: 22
|
You're right
I was sure I could not have done a mistake on such a simple library call... The debugger helped me realise that I forgot about about the '#' before the constant name the correc line is: move.l #VIEWPORT_EXTRA_TYPE,d0 As a matter of fact, I used VIEWPORT_EXTRA_TYPE as ram address... . Now it works ok. I know that the viewport functions are low level and that using them myself means sort of taking over the machine. My main goal is an AGA display that is system friendly, so I suppose that using proper Intuition screens do not impact performance and enables mouse functions. Right? As an extreme example, do you think it would be possible/feasible to code a smooth, coloured and fast platform scrolling game using an intuition screen and OS system friendly calls? I suppose a 68000 A500 without fastram would probably suffer performance issues. Perhaps 68020 A1200 could make it, with at least some fast memory |
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Unexpected surprise inside A500 | gunni | support.Hardware | 20 | 25 August 2011 21:14 |
What a surprise ^^ | dlfrsilver | Retrogaming General Discussion | 8 | 02 June 2006 13:59 |
Surprise!! | Steve | project.SPS (was CAPS) | 2 | 22 April 2003 02:29 |
surprise productions | thinlega | Amiga websites reviews | 2 | 31 December 2002 20:48 |
WHD patch for Fireforce (What a surprise!) | MethodGit | Amiga scene | 5 | 13 August 2001 00:16 |
|
|