I have an app with a source list. In Lion, it works wonderfully. In Mountain Lion, it works fine, but there's an unwanted side effect. Whenever the selected row changes in the source list, Mountain Lion will scroll that row to the top of the scroll view. This happens whether the change happens due to a click or via code. As I said, it doesn't happen in Lion, only Mountain Lion.
Has anyone experienced anything like this themselves?
Related
I have an app developped under Xcode7 in 10.10
I changed the deployment target system to 10.8 because of the IT situation of another school.
The 10.8 app runs fine under 10.10, but on an 10.8 machine, I only see a window grayed out in the face of the MainMenu.xib included the menus, but inactive. Its reaction are as in IB. The previous login windows called at startup are not shown.
In the console I only see a warning about 'Invalid color System labelColor'.
Explanation:
I reduced my project to the Start nib window and the MainMenu.xib. I looked for labelColor in every single nib and xib file with BBedit.
When I compile, I look in the content of the compiled app and can find a MainMenu.nib (not xib) with a single String Item labelColor.
Runnig the app in 10.10 is fine, but in 10.9 the warning appears.
Explanation 2:
Problem fixed: The labelColor is inserted in 10.10/Xcode7 with an NSBox inserted in IB. Obviously this was changed when I transfered the rather old project to Xcode7. I don't know if this is changeble.
I'm having some trouble on making an app compatible with Mavericks.
I was wondering : Did Apple change something in the UI element hierarchy for the Dock ?
Here is what I have on Mavericks using Accessibility Inspector
I guess not. This is what I get with Mountain Lion (v10.8.5):
Since upgrading to XCode 5 and Mountain Lion, Xcode is always behind all other windows.
For instance, I open up Safari or Finder to look at something and I have to close or minimize them in order to get back to XCode. With XCode 4 I would leave several windows open and just click between them.
I know this is probably some stupid OSX setting that got changed in upgrading to Mountain Lion, but for the life of me I know not what!
Thanks in advance!
It wasn't working Friday, works fine today (Monday).
Go figure!
I was developing an app for Mac OS X. I migrated to OSX 10.8 yesterday and found that WebView's "Inspect Element" is no longer usable. With the same source repo which works well under 10.7 LION, the new build just shows menuitem there but do nothing after clicking. I dug for a while and found that my implementation of WebUIDelegate cause this problem (in 10.8 mountain lion ONLY)
Even this won't work:
- (NSArray *)webView:(WebView *)sender
contextMenuItemsForElement:(NSDictionary *)element
defaultMenuItems:(NSArray *)defaultMenuItems
{
return defaultMenuItems;
};
If I comment the whole function above, that "inspect element" does work well.
I don't know if this is a bug or there is anything that I missed.
I believe you're running in to a symptom of the issue described in WebKit bug 89323. It was fixed in Safari 6.0.2.
I've just installed OS X Lion and XCode 4.1.
I have an app that opens the last used document automatically at startup. To do so I have implemented applicationShouldHandleReopen.
This app used to launch fine from XCode 4.0.2 on Snow Leopard.
After I compiled my app with XCode 4.1 it stopped working.
I put a break point inside applicationShouldHandleReopen, but it never breaks unless I click on the app icon on dock.
When I double click the app in Finder as opposed to running it from XCode 4.1, it works as expected; it launches the last document, meaning applicationShouldHandleReopen must have been called at startup.
Any ideas what happened? What should I do to bring back the old behavior?
Or do you think this is a bug in XCode 4.1?
Thanks
This is no longer an issue. I don't observe this behavior any more.