Re: [info-performer] Multipipe Initialization

Date view	Thread view	Subject view	Author view

From: Christopher D. Johnson (cubicwts++at++excite.com)
Date: 10/06/2005 08:18:44

Next message: Jason Daly: "Re: [info-performer] Multipipe Initialization"
Previous message: Christopher D. Johnson: "Re: [info-performer] Multipipe Initialization"
Maybe in reply to: Christopher D. Johnson: "[info-performer] Multipipe Initialization"
Next in thread: Jason Daly: "Re: [info-performer] Multipipe Initialization"

Actually, I am catching x-events so that I can detect "mouse events" when someone touches the lower LCD touch-screen. The window I am creating for the lower screen does not show any mouse pointer but it does have "buttons" on it that can be pressed.

Christopher D. Johnson
AV-8B Harrier II Simulators
ISEO Support Team
Cherry Point, NC
252-466-4542
252-466-4538

--- On Thu 10/06, Rick van Haasen < rick.van.haasen++at++philips.com > wrote:
From: Rick van Haasen [mailto: rick.van.haasen++at++philips.com]
To: cubicwts++at++excite.com
Date: Thu, 6 Oct 2005 12:51:55 +0200
Subject: Re: [info-performer] Multipipe Initialization

Hi Christopher, why is it that you use these routines for the getting the x-connection? is it for getting the keyboard events? in that case its easier to use functions from pfu, in that case you don't have to do with any X-specific stuff. #include <Performer/pfu.h> pfuEventStream g_events; main() { pfInit() pfuInit() while(handleEvents()) { pfFrame() } } // Handle keyboard events // bool handleEvents() { pfuGetEvents(&g_events); pfuEventStream* pEvents = &g_events; bool cont=true; int numDevs = pEvents->numDevs; for (int j=0 ; j<numDevs ; j++) { int dev = pEvents->devQ[j]; int val = pEvents->devVal[j]; if (pEvents->devCount[dev] > 0) { switch (dev) { case PFUDEV_REDRAW: pEvents->devCount[dev]=0; break; case PFUDEV_WINQUIT: pEvents->devCount[dev]=0; break; case
PFUDEV_KEYBD: for (int i=0 ; i<pEvents->numKeys; ++i ) { int key = pEvents->keyQ[i]; if ( pEvents->keyCount[key] ) { switch ( key ) { case 27: // exit if 'esc' is pressed cont = false; break; default: break; } } } pEvents->devCount[dev] = 0; break; } } } return cont; } Or do you have another reason to specify the server as you are doing? Rick "Christopher D. Johnson" <cubicwts++at++excite.com> 2005-10-05 19:54 Please respond to cubicwts++at++excite.com To Rick van Haasen/EHV/RESEARCH/PHILIPS++at++PHILIPS cc Subject Re: [info-performer] Multipipe Initialization Classification Rick- Something that is stumping me and may be related to my problem
is that I am trying to get the XServer connection in the following way: static void InitXInput() { /* wait for X Window to exist in Performer shared memory */ if (mttGlobal->winLOWER = pfGetPWinWSWindow(mttGlobal->pwinLOWER)) { XSelectInput(mttGlobal->dsp,mttGlobal->winLOWER,KeyPressMask | ButtonPressMask ); XMapWindow(mttGlobal->dsp,mttGlobal->winLOWER); XFlush(mttGlobal->dsp); } } . . . mttGlobal->dsp = pfGetCurWSConnection(); InitXInput(); . . . where mttGlobal->dsp is declared as follows: "pfWSConnection *dsp;" From reading the manual I gather that the call to pfGetCurWSConnection() is supposed to return a pointer of type "pfWSConnection". But when I compile I get warnings on the "mttGlobal->dsp = pfGetCurWSConnection();" line as well as XSelectInput, XMapWindow, and XFlush warning of an incompatable pointer
type. Why would it complain about "mttGlobal->dsp = pfGetCurWSConnection();"? And how can I convert the mttGlobal->dsp from a pfWSConnection to a Display connection? Seems the manual is saying one thing and I'm getting something else. <stumped> Christopher D. Johnson AV-8B Harrier II Simulators ISEO Support Team Cherry Point, NC 252-466-4542 252-466-4538 --- On Wed 10/05, Rick van Haasen < rick.van.haasen++at++philips.com > wrote: From: Rick van Haasen [mailto: rick.van.haasen++at++philips.com] To: cubicwts++at++excite.com Date: Wed, 5 Oct 2005 15:49:23 +0200 Subject: Re: [info-performer] Multipipe Initialization you are right, i get this warning, but after that the application continues, running fullscreen on all 4 monitors. Sometimes however the application seriously drops framerate, i haven't found why, this can be a problem in my application, maybe something else. Anyway, the
application runs without crashing. I don't think the warning is fatal...... I just started another project, my code is at this stage just "basic setup stuff and calling while (1) pfFrame;" I get the warning, next the application shows a black screen as expected. Does (on your system) such a "minimal code" crash the after the warning? Rick. "Christopher D. Johnson" <cubicwts++at++excite.com> 2005-10-05 15:32 Please respond to cubicwts++at++excite.com To Rick van Haasen/EHV/RESEARCH/PHILIPS++at++PHILIPS cc Subject Re: [info-performer] Multipipe Initialization Classification Wow, so you are getting that message and your pfPipeWindows are still coming up properly? I have been so focused on getting my x calls to find the lower window properly (that's the portion of the program that
 is causing the application to bomb and exit) I haven't taken the x calls out to see if the windows are running properly once I get to m y main graphical loop. So you say y our windows are "working" even though Performer give you the "PF Notice: pfChooseFBConfig: failed to make configuration mathcing specified attributes" notice? Christopher D. Johnson AV-8B Harrier II Simulators ISEO Support Team Cherry Point, NC 252-466-4542 252-466-4538 --- On Wed 10/05, Rick van Haasen < rick.van.haasen++at++philips.com > wrote: From: Rick van Haasen [mailto: rick.van.haasen++at++philips.com] To: rick.van.haasen++at++philips.com Cc: cubicwts++at++excite.com, info-performer++at++sgi.com, owner-info-performer++at++performer.engr.sgi.com Date: Wed, 5 Oct 2005 14:54:24 +0200 Subject: Re: [info-performer] Multipipe Initialization Hi, i have to come back on my
previous findings: the issue is NOT solved by explicitely setting the visualId's ! most likely i missed the warning message (the application outputs much of info on the console) So i do get the warning/notice: PF Notice: pfChooseFBConfig: failed to make configuration mathcing specified attributes. sorry for the misleading info in my previous reply.... :-( Rick. Rick van Haasen <rick.van.haasen+FromInternet++at++philips.com> Sent by: owner-info-performer++at++performer.engr.sgi.com 2005-10-04 14:28 Please respond to Rick van Haasen/EHV/RESEARCH/PHILIPS++at++PHILIPS To cubicwts++at++excite.com cc info-performer++at++sgi.com owner-info-performer++at++performer.engr.sgi.com Subject Re: [info-performer] Multipipe Initialization Classification Hi, I
 had more or less the same situation with 4 screens (2 graphics cards, each card using 2 monitors, using twinview on each card, effectively using 2 "x-screens" where each screen covers 2 monitors). I found out that the message has to to with the fact that each x-screen uses different visual id's for effectively the same visual: if you run glxinfo you can verify this. So if performer first determines a visual-id on 1 screen, and then tries to use this id to create the visuals on both screens it will fail on 1 of the other screen. I verified this by explicitely requesting the visual: pViewer->getPipe(0)->getPWin(0)->setVisualId(0x47); // pViewer is a pointer to pfvViewer pViewer->getPipe(1)->getPWin(0)->setVisualId(0x16a); .......blabla pViewer->config(); (In this system i use 2 nvidia
quadro fx1400 cards, using the latest drivers) this way i didn't get the warning anymore. So it seems like a Performer issue to me..... Rick. "Christopher D. Johnson" <cubicwts++at++excite.com> Sent by: owner-info-performer++at++performer.engr.sgi.com 2005-10-03 20:31 Please respond to cubicwts++at++excite.com To info-performer++at++sgi.com cc Subject [info-performer] Multipipe Initialization Classification Greetings all. I have a simulation program running on a dual processor PC. There is an upper and a lower LCD display, with the lower LCD being a touch screen. The lower screen is "display 0" while the upper screen is "display 1". What I am trying unsuccessfully to do is initialize performer so that I have 2
 pfPipes created (one for each display) and each pfPipe has just a single pfPipeWindow attached to it. Everything initializes seemingly fine until I call pfFrame() for the first time, at which time I see my full screen windows created (blank) on the uper and lower display, and then it bombs out (the screens disappear) and I get the following notice: "PF Notice: pfChooseFBConfig: failed to make configuration matching specified attributes" Below that I get a "BadWindow" message as my X calls try to operate on the lower window created. Simply going back to one pipe, one window runs fine. Here are the functions I am using to initialize performer and initialize the pfPipes and pfPipeWindows. I've looked in the Performer manual and tried to set the pipes and windows up to work properly, but obviously I am
 missing something. Any clues? static void initPerformer(void) { void *arena = NULL; pfSharedArenaSize(134217728); /* 128 * 1024 * 1024 = 128 Mb */ // pfSharedArenaSize(167772160); /* 160 * 1024 * 1024 = 128 Mb */ // pfSharedArenaSize(268435456); /* 256 * 1024 * 1024 = 256 Mb */ pfInit(); arena = pfGetSharedArena(); /* Allocate Global Variables */ mttGlobal = pfMalloc(sizeof(global_t), arena); MttGfx = pfMalloc(sizeof( MTTGFX ), arena); c_ = pfMalloc(sizeof( struct ForCComm ), arena); ntReq = pfMalloc(sizeof(NTREQ), arena); Client = pfMalloc(sizeof( CLIENT ), arena); BBoxTerrain = pfMalloc(sizeof ( pfBox ), arena); /* initialize global values */ initGlobal(); 
 /*------------------------------------------------------ * Initialize main Gfx variables. *-----------------------------------------------------*/ initGfx(); readConfigFile(); // pfMultiprocess(PFMP_DEFAULT); pfMultiprocess(PFMP_FORK_DBASE | PFMP_FORK_LPOINT); pfMultipipe(2); // scb - uncommented Multithread(...) /* pfMultithread(0, PFPROC_CULL, 2); */ pfdInitConverter("flt"); pfConfig(); pfFilePath( "../data/"); pfNotifyLevel(PFNFY_FATAL); #ifdef GFXAUTOSYNC pfFrameRate(MttGfx->FrameRate); pfPhase(PFPHASE_LOCK); #endif } static void OpenPipeWin(pfPipeWindow *pwin) { pfOpenPWin(pwin); } static void initPipeWindow(void) { int constraints[] = { PFFB_DOUBLEBUFFER, PFFB_RGBA, 
 PFFB_RED_SIZE, 5, PFFB_GREEN_SIZE, 5, PFFB_BLUE_SIZE, 5, PFFB_ALPHA_SIZE, 1, PFFB_STENCIL_SIZE, 8, PFFB_DEPTH_SIZE, 15, (int)NULL }; /*------------------------------------------------------ * Configure graphics pipeline. *-----------------------------------------------------*/ mttGlobal->gfxPipeLOWER = pfGetPipe(0); if (!(mttGlobal->gfxPipeLOWER)) { fprintf(stderr, "ERROR: Unable to initialize (pfPipe *) LOWER!\n"); abort(); } mttGlobal->gfxPipeUPPER = pfGetPipe(1); if (!(mttGlobal->gfxPipeUPPER)) { fprintf(stderr, "ERROR: Unable to initialize (pfPipe *) UPPER!\n"); abort(); } pfPipeScreen(mttGlobal->gfxPipeLOWER,0); pfPipeScreen(mttGlobal->gfxPipeUPPER,1); mttGlobal->pwinLOWER =
 pfNewPWin(mttGlobal->gfxPipeLOWER); if (!(mttGlobal->pwinLOWER)) { fprintf(stderr, "ERROR: Unable to initialize (pfWindow *) LOWER!\n"); abort(); } mttGlobal->pwinUPPER = pfNewPWin(mttGlobal->gfxPipeUPPER); if (!(mttGlobal->pwinUPPER)) { fprintf(stderr, "ERROR: Unable to initialize (pfWindow *) UPPER!\n"); abort(); } pfPWinName(mttGlobal->pwinLOWER,MttGfx->ScreenLOWER.Name); pfPWinType(mttGlobal->pwinLOWER, PFWIN_TYPE_X); pfPWinMode( mttGlobal->pwinLOWER, PFWIN_NOBORDER, 1); pfPWinConfigFunc( mttGlobal->pwinLOWER, OpenPipeWin); pfChoosePWinFBConfig( mttGlobal->pwinLOWER, constraints); pfConfigPWin( mttGlobal->pwinLOWER ); pfPWinOriginSize(mttGlobal->pwinLOWER, 0, 0, MttGfx->ScreenLOWER.SizeW, MttGfx->ScreenLOWER.SizeH); 
 //pfPWinScreen(mttGlobal->pwinLOWER,0); pfOpenPWin(mttGlobal->pwinLOWER); pfPWinName(mttGlobal->pwinUPPER,MttGfx->ScreenUPPER.Name); pfPWinType(mttGlobal->pwinUPPER, PFWIN_TYPE_X); pfPWinMode( mttGlobal->pwinUPPER, PFWIN_NOBORDER, 1); pfPWinConfigFunc( mttGlobal->pwinUPPER, OpenPipeWin); pfChoosePWinFBConfig( mttGlobal->pwinUPPER, constraints); pfConfigPWin( mttGlobal->pwinUPPER ); pfPWinOriginSize(mttGlobal->pwinUPPER, 0, 0, MttGfx->ScreenUPPER.SizeW, MttGfx->ScreenUPPER.SizeH); //pfPWinScreen(mttGlobal->pwinLOWER,1); pfOpenPWin(mttGlobal->pwinUPPER); /* set off the draw process to open windows and call init callbacks */ pfFrame(); sleep(3); pfPWinFullScreen( mttGlobal->pwinLOWER ); pfPWinFullScreen( mttGlobal->pwinUPPER ); 
mttGlobal->dspLOWER = pfGetCurWSConnection(); // Logic To Set Up Catching Of X-Events on the lower touch screen mttGlobal->winLOWER = pfGetPWinWSWindow(mttGlobal->pwinLOWER); XSelectInput(mttGlobal->dspLOWER,mttGlobal->winLOWER,KeyPressMask | ButtonPressMask ); XMapWindow(mttGlobal->dspLOWER,mttGlobal->winLOWER); XSync(mttGlobal->dspLOWER,FALSE); /*------------------------------------------------------ * Remove cursor arrow. *-----------------------------------------------------*/ #ifndef TESTMTT pfuLoadPWinCursor(mttGlobal->pwinLOWER, PFU_CURSOR_OFF); #endif } Christopher D. Johnson AV-8B Harrier II Simulators ISEO Support Team Cherry Point, NC 252-466-4542 252-466-4538 _______________________________________________ Join Excite! -
 http://www.excite.com>The most personalized portal on the Web! ----------------------------------------------------------------------- List Archives, Info, FAQ: http://www.sgi.com/software/performer/> Open Development Project: http://oss.sgi.com/projects/performer/> Submissions: info-performer++at++sgi.com Admin. requests: info-performer-request++at++sgi.com ----------------------------------------------------------------------- ----------------------------------------------------------------------- List Archives, Info, FAQ: http://www.sgi.com/software/performer/> Open Development Project: http://oss.sgi.com/projects/performer/> Submissions: info-performer++at++sgi.com Admin. requests:
 info-performer-request++at++sgi.com ----------------------------------------------------------------------- _______________________________________________ Join Excite! - http://www.excite.com>The most personalized portal on the Web! _______________________________________________ Join Excite! - http://www.excite.com>The most personalized portal on the Web!

_______________________________________________
Join Excite! - http://www.excite.com
The most personalized portal on the Web!

Next message: Jason Daly: "Re: [info-performer] Multipipe Initialization"
Previous message: Christopher D. Johnson: "Re: [info-performer] Multipipe Initialization"
Maybe in reply to: Christopher D. Johnson: "[info-performer] Multipipe Initialization"
Next in thread: Jason Daly: "Re: [info-performer] Multipipe Initialization"

Date view	Thread view	Subject view	Author view

This archive was generated by hypermail 2b29 : Thu Oct 06 2005 - 08:19:01 PDT