Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uunet!cbmvax!peter
From: peter@cbmvax.commodore.com (Peter Cherna)
Newsgroups: comp.sys.amiga.programmer
Subject: Re: 2.0 Programming Questions
Message-ID: <17277@cbmvax.commodore.com>
Date: 9 Jan 91 16:39:43 GMT
References: <1991Jan9.101407.11809@marlin.jcu.edu.au>
Reply-To: peter@cbmvax.commodore.com (Peter Cherna)
Organization: Commodore, West Chester, PA
Lines: 37

In article <1991Jan9.101407.11809@marlin.jcu.edu.au> glmwc@marlin.jcu.edu.au (Matt Crowd) writes:
>I am trying to get a program to work so that it will correctly
>open a screen that is 256 lines high when running under 2.0 on
>a PAL workbench.. but on an NTSC machine! (if you can understand
>that!)
>
>At the moment I am testing the DisplayModes flag, but this 
>only checks that hardwired jumper.  I have heard that the 2.0
>calls GetDisplayInfoData() in conjunction with DisplayInfo.PropertyFlags
>DIPF_IS_PAL or the LockPubScreen() call.  However, besides that
>I have absolutely no idea how to use the calls etc. (no manuals
>etc).  Can anybody help?  (parameters, return values etc)


Something like this:

	ULONG modeID = HIRES_KEY;	/* some reasonable default */
	struct Screen *wbscreen;

	if ( wbscreen = LockPubScreen( "Workbench" ) )
	{
		modeID = GetVPModeID( &wbscreen->ViewPort );
		UnlockPubScreen( NULL, wbscreen );
	}

	myscreen = OpenScreenTags( &mynewscreen,
		SA_DisplayID, modeID,
		TAG_DONE);

>Colin Adams

     Peter
--
     Peter Cherna, Software Engineer, Commodore-Amiga, Inc.
     {uunet|rutgers}!cbmvax!peter    peter@cbmvax.commodore.com
My opinions do not necessarily represent the opinions of my employer.
"Oh, PIN-compatible!  I thought you wanted me to make it IN-compatible!"