• Advertisement


  • Content count

  • Joined

  • Last visited

Community Reputation

102 Neutral

About BackFlipp

  • Rank
  1. I'm listening to Serendipity by Tom Middleton on Pandora http://t.co/qv2AOfau #pandora
  2. Sure, NOREMOVEchecks if there's a message on the queue and returns true if there is. Then, you use GetMessage to pull it off the queue and process it. You're right that looping on it until all messages have been processed is the better way to do it (even better: render in a separate thread, so you don't slow your render loop if processing tons of input/messages). That said, it doesn't give any insight as to why the behavior is different. In both the first and second cases, the message queue is processed successfully; messages are caught, translated, and passed. Starting fullscreen or windowed works in both, but switching contexts via alt-enter doesn't work in the latter.
  3. I'm listening to Burning Ice by Stratosphere on Pandora http://t.co/mo5XllAy #pandora
  4. Heya all I'm following the DirectX tutorial here: [[url="http://www.directxtutorial.com/Tutorial11/B-A/BA4.aspx#still"]1[/url]] I've found some strange behavior with the main loop... The tutorial uses the following [code]while(TRUE) { if(PeekMessage(&msg, NULL, 0, 0, PM_REMOVE)) { TranslateMessage(&msg); DispatchMessage(&msg); if(msg.message == WM_QUIT) break; } RenderFrame(); } [/code] When you hit alt-enter to switch to fullscreen mode, it works flawlessly. However, if you change the main loop to this: [code]while(TRUE) { if(PeekMessage(&msg, NULL, 0, 0, PM_NOREMOVE)) { GetMessage(&msg, NULL, 0, 0); DispatchMessage(&msg); if(msg.message == WM_QUIT) break; } RenderFrame(); } [/code] When you hit alt-enter, it starts to go fullscreen, then "dings" an error and returns. It seems like it has to do with the PM_NOREMOVE flag, as the following shows the same broken behavior as the latter: [code]while(TRUE) { if(PeekMessage(&msg, NULL, 0, 0, PM_NOREMOVE)) { } if(PeekMessage(&msg, NULL, 0, 0, PM_REMOVE)) { DispatchMessage(&msg); if(msg.message == WM_QUIT) break; } RenderFrame(); } [/code] The DirectX debugging output doesn't give any errors or warnings. Interestingly, it has to do with the context switching itself, not the fullscreen... if you change the line: [code]swapChainDesc.Windowed = false;[/code] It starts fine in fullscreen, but fails to switch out of fullscreen on alt-enter. Any reason why PM_NOREMOVE would break fullscreen switching? [1] [url="http://www.directxtutorial.com/Tutorial11/B-A/BA4.aspx#still"]http://www.directxtu.../BA4.aspx#still[/url]
  5. I'm listening to 8:07 by Global Communication on Pandora http://t.co/EsfTqQz7 #pandora
  6. I'm listening to Okinawa Sunset by Johan Gielen on Pandora http://t.co/FDJrcUVr #pandora
  7. I'm listening to Untitled Dub With Noises by Christopher Lawrence on Pandora http://t.co/f5CrKuHN #pandora
  8. I'm listening to Mana by Shiloh on Pandora http://t.co/n6MCSWBC #pandora
  9. I'm listening to So Flows The Current by Patrick O'Hearn on Pandora http://t.co/dQrc9cyC #pandora
  10. I'd suggest getting familiar with CMAKE. It's a bit convoluted to learn, but once you get it up and running it can automatically generate VS project files on Windows and Linux. I haven't used it with Mac, but I would imagine it would be able to do the same.
  11. Heya! I'm very new to XCode's IDE so bear with me here. I've got two xcodeproj projects: A and B. A builds a framework, and B links to it via B->External Frameworks And Libraries->A.framework. Both are set to build to the $(PROJECT)/builds/Development directory, and do so successfully. When I run B from within XCode after building it, it starts up successfully and runs. However, when I open a terminal and navigate to $(PROJECT)/builds/Development and run ./B, it fails with the error "dyld: Library not loaded: @executable_path/.../Frameworks/A.framework/Versions/A/A". Now, as far as I can tell, the only thing that can possibly change between the two settings (XCode vs Terminal) is some path environment variable that is set in XCode that isn't present in the Terminal. So, a few questions: 1. Why would it successfully find the A framework when I run it from XCode, when there is no "Frameworks" folder anywhere inside side the project? 2. I have the "Framework Search Paths" set up for $(PROJECT)/builds/Development, but it doesn't seem to do anything. Is that only for building? 3. Does setting A's "Dynamic Library Install Name" to something like "@executable_path/.../Frameworks" require that any executable that uses it be located relative to it? It seems a little backwards to require that the app be located relative to the framework. On Linux, you'd install the library to /usr/local/lib and the executable anywhere you'd want, ya? Thanks!
  12. I'm listening to Another New Day by Jazzanova on Pandora http://t.co/hPjSAdJN #pandora
  • Advertisement