Welcome, Guest. Please login or register.

Author Topic: Retarget(t)able graphics  (Read 3064 times)

Description:

0 Members and 1 Guest are viewing this topic.

Offline KarlosTopic starter

  • Sockologist
  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Nov 2002
  • Posts: 16879
  • Country: gb
  • Thanked: 5 times
    • Show all replies
Retarget(t)able graphics
« on: May 06, 2003, 11:36:48 PM »
Hi all,

Does anybody know how compatible Picasso96 is for applications devloped for cybergraphx?

Some of my code uses cybergraphx calls for direct access and also getting infromation from cybergraphics mode lists. I also use the special flags for allocating 15/16/32-bit bitmaps with AllocBitMap().

Other than that, its all OS 3.x standard stuff.

Does anybody know how compatible p96 is with cgx? Are there any no go areas or performance killers? I'm only really interested in 15-bit modes and above.

Sorry for the hand-wavy questioning, I'm just after some general compatibility info.

Thanks,

K
int p; // A
 

Offline KarlosTopic starter

  • Sockologist
  • Global Moderator
  • Hero Member
  • *****
  • Join Date: Nov 2002
  • Posts: 16879
  • Country: gb
  • Thanked: 5 times
    • Show all replies
Re: Retargetable graphics
« Reply #1 on: May 07, 2003, 10:58:36 PM »
Quote

Billsey wrote:
I looked at the subject for this thread and thought it said, "Regrettable Graphics". :lol:


:-D My bad spelling I guess...One T or two in retarget(t)able?

I might end up regretting anything that messes up my code under p96!

So, from the responses here I take it that compatibility is very good. Shame LockBitMap() locks the whole system - I do rendering to offscreen buffers and the like.

@everybody - thanks for the info...
int p; // A