I am currently simply trying to build a simple screen saver in xcode 3.2 on osx 10.6.3 using an openGL view as described in this article: http://cocoadevcentral.com/articles/000089.php anyways even if I use the exact same code from the example all I see when testing the screen saver is a black screen. I looked in OSX Console if it tells me anything useful. the only thing I get is something like this:
[0x0-0x1e01e].com.apple.systempreferences[629] System
Preferences(629,0x7fff71071be0)
malloc: reference count underflow for
0x20057be80, break on
auto_refcount_underflow_error to
debug. System Preferences[629] invalid
context
I have no idea what is wrong, so I would be glad if someone could tell me how to use openGL together with the screensaver template in xCode 3.2. Also, is there a way to make another target so I can preview the screensaver from within xCode?
Thanks!
The example on Cocoa Dev Central works just fine. The same error comes up for me, but as far as I can tell, that is not the reason why you're getting a black screen.
I had a similar problem because I wasn't correctly reinstalling the screen saver.
Make sure you quit System Preferences before reinstalling the screen saver. If you don't, the old screen saver will still be used, even when it asks you about overwriting it.
Related
I have a problem in my existing macOS project.
My windows/views render all blurry on a retina Mac when I run it.
It look perfectly fine in Xcode when working with the storyboard.
If I add a new window to my existing app it looks like this (all blurry):
while when I do a new project it looks like this (perfectly sharp):
i am searching for what might cause this for hours now but am still without a clue.
Does anyone know what might influences the rendering of my macOS app?
Turns out I had to set
NSHighResolutionCapable
to
yes
in my projects plist file.
Not sure tho what exactly is different on the "new" project that removes the necessity to do this.
with this property my old project is rendering properly now.
I know this feature is very new, so I'm hoping someone has had experience with this issue before and may shed some light on what might be going on. Right now we are trying to utilize Xamarin 4.2's new "remote iOS simulator for Windows". When I build to Mac simulator, it works fine the app shows up and no issues. When I turn on the option to use the remote simulator, the simulator opens, and then there's just a blank screen, as you can see from the screenshot there's no errors and it built fine:
Looks like you are hitting the following:
https://bugzilla.xamarin.com/show_bug.cgi?id=42333
The remote simulator is in preview, so there are likely to be bugs that have not been fixed yet. I'd suggest adding a comment to that bug report with any information you can provide.
If you would like to receive a notification when the bug is updated, you can add yourself to the CC list for the bug. Please note that you will need to create an account on that system if you have not already done so.
I am totally new to xcode and macbook , i have developed a small ios application for ipad air running which in emulator is showing me white blank screen so thought of running it in terminal to debug the program , can anyone help me with this
Thank you
If your project builds and runs and shows a white screen in the simulator, there is likely a logic error in your code. If you want to make a console application you would have to create an osx command line project. Google debugging in xcode. Try a beginners tutorial that you can follow along and make something appear on your screen. Sprite kit games are easy to make and give quick results and satisfaction. Take a look at this tutorial for basic sprite kit game.
Sounds like you forget to set rootview controller . Go to your storyboard and check Initailview controller is enable or disable
Xcode 4.2+ and Xcode 5 have a very powerful debugger for OpenGL ES. Until recently, the debugger itself would crash often (it didn't work reliably for me until Xcode5.0), but it sometimes disables itself and refuses to run at all.
This being an Apple application, they don't bother with error messages, they simply refuse to let you press the Analyze button:
I can't find any reference in Apple's docs to a situation that would "disable" the analysis. I know that it can work on this machine, because it worked fine on a different device.
Device that works:
iPad3, running iOS 6.x
Device that Xcode5 refuses to work with:
iPad Mini, running iOS 7.x
...I've tried updating to latest 7.x - no change. Xcode just refuses to work properly. All other debugging works fine.
It's not a perfect answer, but I've noticed something that might explain it...
When you pause the debugger, this triggers the button to grey-out. So, if you needed to analyse the frame at a particular point in your app ... you can't.
It sucks, and I have no idea how you're supposed to debug something without using the debugger, but ... it might be why I was getting disabled button!
Just cannot find UI for enabling the opengl es frame capture.
I know in xcode 4.2 document, the interface is in Edit Scheme as link below. But not found in 4.3 at this place.
http://developer.apple.com/library/ios/#documentation/DeveloperTools/Conceptual/WhatsNewXcode/Articles/xcode_4_2.html#//apple_ref/doc/uid/00200-SW1
There is no longer a check box to enable this.
You need to have the OpenGLES.framework in the Project Navigator for the camera icon to appear. (I have several apps with it included via linker settings, which is not picked up).
If it still fails, try removing it and re-adding it, and also add it to your Build Phases/Link Binary With Libraries. I've found this to be pretty reliable.
Capture GPU Frame is greyed out for me when I run a simulator. It seems like it needs a real device.