Welcome, Guest. Please login or register.

Author Topic: Amiga C - GUI Question  (Read 1388 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline Pat the Cat

Re: Amiga C - GUI Question
« on: February 02, 2017, 11:22:08 PM »
It is kind of a first step when writing software - do I want GUI interface windows, or am I going to do all that myself?

It was a big thing to turn off the OS and do all the work yourself. If the OS was going to be a hindrance for what you were trying to program, you turned it off, either right at the beginning, or selectively in the main body of code for events that needed a little privacy and complete control of resources. The snag with the latter method, you got a glitch when handing back control and telling the GUI to clear the screen and redraw everything (this is observable behaviour with some software).
"To recurse is human. To iterate, divine."

A1200, Vanilla, Surf Squirrel, SD Card, KS 3.0/3.z, PCMCIA dev
A500, Vanilla, A570, Rev 5, KS 1.2/1.3 Testbench system
Rasp Pi, UAE4ARM, 3D laser scanner, experimental, hoping for AmigaOS4Arm, based on Watterott Fabscan Pi
 

Offline Pat the Cat

Re: Amiga C - GUI Question
« Reply #1 on: February 04, 2017, 12:20:01 AM »
If the software is pre WB2, it is probably using the arp.library often used just for a file requester window.

This was bundled with the OS 2 and above, but was a separate library on 1.3.
"To recurse is human. To iterate, divine."

A1200, Vanilla, Surf Squirrel, SD Card, KS 3.0/3.z, PCMCIA dev
A500, Vanilla, A570, Rev 5, KS 1.2/1.3 Testbench system
Rasp Pi, UAE4ARM, 3D laser scanner, experimental, hoping for AmigaOS4Arm, based on Watterott Fabscan Pi