NSTableView binding and clickedRow returning -1
Hi Thought I would post something I see as reoccurring problem. Basically, having an NSTableView (wrapped in a custom NSView) setup with bindings works fine. Then, trying to get the double-action/target in IB working has strange behaviour when it comes to fetching clickedRow. *Referring to my own problem at* http://stackoverflow.com/questions/27740666/nstableview-iboutlet-clickedrow-is-always-1 which has been setup like https://developer.apple.com/library/mac/qa/qa1472/_index.html *but also look at these guys* http://www.cocoabuilder.com/archive/cocoa/201667-nstableview-double-click-binding-and-clickedrow.html http://www.geektheory.ca/blog/nstableview-and-nsoutlineview-method-clickedrow-always-returning-1-on-double-click-action/ The action target is called but [_tableView clickedRow] always return -1. Also the parameter for the selector, should it contain all the objects in the table view or just the clicked row object? What could be the underlying problem here? There is a good point mentioned on Stackoverflow that the selector might be called before the actual selection is done... -- Med vänliga hälsningar / Best Regards Hajder ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Blurry is the New Sharp
Leaving aside any discussion of whether it was a good idea to add vibrancy to the OS, I do have a question about how to use it. When a popup window or a pulldown such as a menu appears, using the content of whatever's under it as the source image for vibrancy makes sense because the temporary window is meant to be hovering over other content in the same app. But for a sidebar like the iTunes source view, it just seems wrong to blur in content from whatever other window happens to be open behind the current app. Theoretically the two apps have nothing in common, and blurring in the background app's content doesn't help the user in any way. My app will have a source view, so I'd like to know if there's a way to tell the window server to use only the desktop image to create vibrancy effects in a the sidebar, ignoring any other windows which may lie between my app and the desktop. — Charles ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Blurry is the New Sharp
On Jan 5, 2015, at 7:58 AM, Charles Jenkins wrote: Leaving aside any discussion of whether it was a good idea to add vibrancy to the OS, I do have a question about how to use it. Um, it was a terrible amateurish idea. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Rearranging NSOutlineView via drag-and-drop
In case it helps anyone, here's how my NSOutlineView rearranging story ends. I found that reloadItem: works perfectly well to update disclosure triangles. In my acceptDrop method, I tracked which parent items were affected by the move by adding them to an NSSet, then I use performSelector:withObject:afterDelay: using a 0.2-second delay to call a method which reloads the affected items after giving the drag animation time to complete. But in my app, whether an item has children or not can affect which icon appears beside it in the list. Unfortunately, reloadItem: doesn't request a view, which would call the function that assigns icons, nor can I figure out how to ask the outline for the view after my delegate creates it. Rather than trying to come up with some system to track the views outside of the outine, I gave up and simply use performSelector:withObject:afterDelay using a 0.5-second delay to call a method which reloads the entire outline after a move operation is successful. Now rearranging the tree works as expected and both the disclosure triangles and the item icons get updated properly. — Charles On Sunday, January 4, 2015 at 22:07, Charles Jenkins wrote: Thanks, all. I’ll reload parent items. In my app, whether an item has children or not can change which icon appears in the tree, and the outline view has no way to know about that without a reload to cause it to requery the delegate. — Charles Jenkins On Sunday, January 4, 2015 at 7:06 PM, Roland King wrote: On 5 Jan 2015, at 02:13, Quincey Morris quinceymor...@rivergatesoftware.com (mailto:quinceymor...@rivergatesoftware.com) wrote: On Jan 4, 2015, at 05:39 , Roland King r...@rols.org (mailto:r...@rols.org) mailto:r...@rols.org wrote: I had to reload the parent row to get it to call the isItemExpandable and other methods to either show a new disclosure triangle or remove one which was no-longer valid. That sounds at least halfway to being a bug. However, since (if I understand you correctly) the rows you’d have to reload are *not* the rows you’re moving/inserting/deleting, then the reloads shouldn’t interfere with the animations. I wonder, also, if expanding or collapsing the affected parents would achieve the same thing, if reloads were actually too drastic somehow. Correct - the rows I was reloading were not the ones inserted or removed. I am allowing the user to drag a row onto another row which currently has no children and create a hierarchy there and also to drag a row out of a hierarchy leaving it empty of children. I initially started by having any row which is eligible to have children have a disclosure triangle, even if it didn’t currently have any, but decided it looked rather ugly/non-intuitive in this particular case because everything is really eligible. So when a row is added/deleted/moved I check the parent row(s) before and after status to see if its ‘having children’ state changed, if it has, I reload that parent row only which causes the isItemExpandable etc to be called again and shows/hides the disclosure as appropriate. Is it a bug? Possibly. It would certainly not be unreasonable for the outline view to re-query the parents of rows after table changes to see if they should be re-drawn. Depends a bit on whether you see the expandability of a row as being a fairly static property independent of whether it currently has children or something often queried. I can see it both ways, it was very obvious what needed to be done and it was barely a few lines of code to do it so I put it down to my use case of wanting to change indicators and continued on. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com (mailto:Cocoa-dev@lists.apple.com)) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com (http://lists.apple.com) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/cejwork%40gmail.com This email sent to cejw...@gmail.com (mailto:cejw...@gmail.com) ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
URLByResolvingBookmarkData not case sensitive
I am using URLByResolvingBookmarkData . If I make a Bookmark to a file: /Volumes/Macintosh HD/Documents/MyFile.txt and later resolve it with URLByResolvingBookmarkData, I get the original path as expected. Then if I change the filename to MYFILE.txt in the Finder and resolve the bookmark again, the URL is still the mixed-case path above instead of the new uppercase file path. I would expect to get the current path in a case sensitive way. ?? Trygve ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Blurry is the New Sharp
On Jan 5, 2015, at 11:00:57, Paul Scott psc...@skycoast.us wrote: On Jan 5, 2015, at 5:01 AM, Alex Zavatone z...@mac.com wrote: On Jan 5, 2015, at 7:58 AM, Charles Jenkins wrote: Leaving aside any discussion of whether it was a good idea to add vibrancy to the OS, I do have a question about how to use it. Um, it was a terrible amateurish idea. And a waste of time that should have been spent elsewhere.___ I don't think the time it takes to render that is anything we should be worried about. It's imperceptive. It looks great behind menus, but really stupid when part of a window is translucent with a blurry background. And then it goes away when the window isn't active. Bwuh?! Why just list type thingies? That's a really dumb decision. Get rid of it on any *part* of a window (but if an *entire* window wants translucency, then do it to the whole thing, not just some section). -- Steve Mills Drummer, Mac geek ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Blurry is the New Sharp
On Jan 5, 2015, at 9:00 AM, Paul Scott psc...@skycoast.us wrote: And a waste of time that should have been spent elsewhere. I usually dislike piling in on Apple's UI blunders, but in this case I'm compelled to agree :-p I honestly thought that in the post-Steve-Jobs era we at least wouldn't get these pointless gee-wow visual effects anymore; he was always very susceptible to them. Apparently someone there saw GPU cycles going unused and decided they needed to find a new excuse to push some pixels around. Scrolling performance in source-list views (i.e. Xcode, Mail) is total sh*t in Yosemite, even on my relatively new MBP, and I blame vibrancy for it. With the insane GPUs we have nowadays, there's no excuse for a simple outline view not to glide up and down at 30fps or more. I guess the best we can do as developers is to vote with our feet by not adopting it in our apps. (I haven't had to deal with an OS X source list in a while; I assume vibrancy has to be opted into? Or at least there's a way to opt out?) —Jens ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Rearranging NSOutlineView via drag-and-drop
On Jan 5, 2015, at 05:12 , Charles Jenkins cejw...@gmail.com wrote: reloadItem: doesn't request a view What does “request a view” mean? ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Blurry is the New Sharp
On Jan 5, 2015, at 5:01 AM, Alex Zavatone z...@mac.com wrote: On Jan 5, 2015, at 7:58 AM, Charles Jenkins wrote: Leaving aside any discussion of whether it was a good idea to add vibrancy to the OS, I do have a question about how to use it. Um, it was a terrible amateurish idea. And a waste of time that should have been spent elsewhere. smime.p7s Description: S/MIME cryptographic signature ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: URLByResolvingBookmarkData not case sensitive
On 5 Jan 2015, at 10:11 AM, Trygve Inda cocoa...@xericdesign.com wrote: I am using URLByResolvingBookmarkData . If I make a Bookmark to a file: /Volumes/Macintosh HD/Documents/MyFile.txt and later resolve it with URLByResolvingBookmarkData, I get the original path as expected. Then if I change the filename to MYFILE.txt in the Finder and resolve the bookmark again, the URL is still the mixed-case path above instead of the new uppercase file path. I would expect to get the current path in a case sensitive way. The following assumes that your problem is that the pathname hasn’t been updated, not that the reconstituted URL no longer gives access to the desired file. If the bookmark no longer works, then ignore the rest of this. What you expect is plausible, but it’s also plausible that it’s not in the API contract: The most that’s directly promised is that the bookmark will be as robust as possible _in gaining access_ to a volume, directory, container, or file. Your expectation isn’t disclaimed, but I don’t think Foundation promises to make good on it. So long as the grants-access promise is kept, it’s not necessary to report the identical URL string you’d get if you passed the current path to +fileURLWithPath: : * We don’t know whether alias resolution even looks at the string you originally put in the bookmark container. It’s an implementation detail; the string you gave might be kept only as a courtesy (or a last resort). We don’t know, and I don’t think we’re supposed to care. * In the Mac’s default case-insensitive HFS+, correcting for case is pointless. The string you asked the container to contain is still fit for purpose. * Presentation to the user don’t enter into it. Path (and URL) strings have never been safe for presentation to users. (To take one example, standard system directories are localized, but the BSD paths never change from their US-English names.) I’m not saying the documentation disclaims your interpretation, just that it leaves it open to Foundation’s doing what you’re seeing. — F ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Blurry is the New Sharp
On 6 Jan 2015, at 4:11 am, Jens Alfke j...@mooseyard.com wrote: I honestly thought that in the post-Steve-Jobs era we at least wouldn't get these pointless gee-wow visual effects anymore; he was always very susceptible to them. Glad I'm not the only one thinking this. It's not just pointless eye-candy, it's actually contrary to usability. In Safari, I'd come to the conclusion that the window frame tint was an indication of whether you were in a private session or a non-private one, but after some time realised that the tint was merely an effect of what colour the content of the web page happened to be that had been scrolled up behind the title bar. A small thing, but nevertheless misleading. It's also completely arbitrary; what meaning does having a blurry translucent background in a souce list (but not for other window content) actually convey? The whole idea should be canned before it becomes more pervasive. It's already a nuisance and causes numerous graphics glitches (e.g weird black outlines around a non-active progress bar when on a vibrant background). Developers have better things to worry about. People suggested that OS X had jumped the shark with Lion. If so, we're into Jaws VIII vs. Godzilla 3D territory now. --Graham ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Blurry is the New Sharp
My app will have a source view, so I'd like to know if there's a way to tell the window server to use only the desktop image to create vibrancy effects in a the sidebar, ignoring any other windows which may lie between my app and the desktop. This is not possible. corbin ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Blurry is the New Sharp
OMG, did they release Xcode 4 again? No? Then what are we talking about? [I’m begging you all to take your opinions on this subject somewhere where I don’t have to see them.] ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Blurry is the New Sharp
On 5 Jan 2015, at 11:58 pm, Charles Jenkins cejw...@gmail.com wrote: if there's a way to tell the window server to use only the desktop image to create vibrancy effects in a the sidebar, ignoring any other windows which may lie between my app and the desktop Would you really want that, even if it could be done? The effect would be that your active window was cutting a hole through the underlying windows to reveal the desktop. As much as the translucency effect is annoying and a performance drag, it is at least consistent with the layered windows metaphor. You'd be better off just making your window entirely opaque, and I think we should be doing that to send Apple the message that we don't want the stinking translucency effect. --Graham ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Blurry is the New Sharp
I'm going to be 51 years old soon. I spend all day long staring at a computer. I've had trouble with eye fatigue for years. Semitransparent windows drive me nuts; to the extent I can turn off the effect I do so. Michael David Crawford, Consulting Software Engineer mdcrawf...@gmail.com http://www.warplife.com/mdc/ Available for Software Development in the Portland, Oregon Metropolitan Area. On Mon, Jan 5, 2015 at 3:38 PM, Graham Cox graham@bigpond.com wrote: On 6 Jan 2015, at 4:11 am, Jens Alfke j...@mooseyard.com wrote: I honestly thought that in the post-Steve-Jobs era we at least wouldn't get these pointless gee-wow visual effects anymore; he was always very susceptible to them. Glad I'm not the only one thinking this. It's not just pointless eye-candy, it's actually contrary to usability. In Safari, I'd come to the conclusion that the window frame tint was an indication of whether you were in a private session or a non-private one, but after some time realised that the tint was merely an effect of what colour the content of the web page happened to be that had been scrolled up behind the title bar. A small thing, but nevertheless misleading. It's also completely arbitrary; what meaning does having a blurry translucent background in a souce list (but not for other window content) actually convey? The whole idea should be canned before it becomes more pervasive. It's already a nuisance and causes numerous graphics glitches (e.g weird black outlines around a non-active progress bar when on a vibrant background). Developers have better things to worry about. People suggested that OS X had jumped the shark with Lion. If so, we're into Jaws VIII vs. Godzilla 3D territory now. --Graham ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/mdcrawford%40gmail.com This email sent to mdcrawf...@gmail.com ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: NSVisualEffectView NSVisualEffectBlendingModeBehindWindow transparency
On Dec 26, 2014, at 2:26 AM, Jacek Oleksy jole...@opera.com wrote:
Hi,
I add vibrancy effect to my window using the following code:
In the view class:
- (void)awakeFromNib {
NSVisualEffectView* vibrantView = [[NSVisualEffectView alloc]
initWithFrame:self.frame];
vibrantView.appearance = [NSAppearance
appearanceNamed:NSAppearanceNameVibrantLight];
[vibrantView setAutoresizingMask:NSViewWidthSizable | NSViewHeightSizable];
[self addSubview:vibrantView];
}
It uses default blending mode (which is
NSVisualEffectBlendingModeBehindWindow), and this is what I need.
Problem: the vibrancy effect goes right to the bottom of the desktop,
i.e. the color of desktop background color shines through (even if
there are some other windows in the way!).
This is the explicit HI design; it includes a certain percentage of the desktop
image in the blur.
The effect that I need is to have the transparency effect include only
the top visible window, this is how NSPopover works:
In view controller:
@interface PopoverController : NSViewController {
}
@end
@implementation PopoverController
- (void)loadView {
self.view = [[NSView alloc] initWithFrame:NSMakeRect(10,10,100,100)];
}
@end
- (void) viewDidAppear {
NSPopover* popover = [[NSPopover alloc] init];
PopoverController* controller =[[PopoverController alloc] init];
[popover setContentViewController:controller];
[popover setBehavior:NSPopoverBehaviorTransient];
[popover showRelativeToRect:self.view.bounds ofView:self.view
preferredEdge:NSMaxYEdge];
}
The popup that is created gets the vibrancy effect only from the
window that is right below it.
Any ideas on how to make it work for custom window?
There is not any API to control this option. Please log a bug requesting this
ability.
Thanks,
corbin
Thanks,
Jacek
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/corbind%40apple.com
This email sent to corb...@apple.com
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
Re: Blurry is the New Sharp
On 6 Jan 2015, at 07:38, Graham Cox graham@bigpond.com wrote: On 6 Jan 2015, at 4:11 am, Jens Alfke j...@mooseyard.com wrote: I honestly thought that in the post-Steve-Jobs era we at least wouldn't get these pointless gee-wow visual effects anymore; he was always very susceptible to them. Glad I'm not the only one thinking this. It's not just pointless eye-candy, it's actually contrary to usability. In Safari, I'd come to the conclusion that the window frame tint was an indication of whether you were in a private session or a non-private one, but after some time realised that the tint was merely an effect of what colour the content of the web page happened to be that had been scrolled up behind the title bar. A small thing, but nevertheless misleading. It's also completely arbitrary; what meaning does having a blurry translucent background in a souce list (but not for other window content) actually convey? The whole idea should be canned before it becomes more pervasive. It's already a nuisance and causes numerous graphics glitches (e.g weird black outlines around a non-active progress bar when on a vibrant background). Developers have better things to worry about. People suggested that OS X had jumped the shark with Lion. If so, we're into Jaws VIII vs. Godzilla 3D territory now. —Graham I was wondering why this wasn’t annoying me, then I remembered I turned all this crp off months ago with the ‘reduce transparency’ toggle on the accessibility panel. I found having shadowy bits of whatever was last front before I switched to Xcode or Mail under the navigator was just confusing. The effect is also limited to the frontmost window, which leads to the odd effect where if you have say Xcode over Safari, you get bleedthrough of Safari in the Xcode window, but if you then pull up something very small, like calculator, something not full-screen, the bleedthrough between Safari and Xcode disappears again because now Calculator is frontmost, Xcode is behind it and Safari is the third window. As you toggle back and forth the blurry shadow guff appears and disappears which is really jarring. I even filed it as a bug, noting that the entire effect was ghoulish to start with but if it was going to be done, at least do it consistently. I’ll toggle reduce transparency back on again and return to sanity. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Blurry is the New Sharp
On Tue, Jan 6, 2015 at 12:38 AM, Graham Cox graham@bigpond.com wrote: It's not just pointless eye-candy, it's actually contrary to usability. In Safari, I'd come to the conclusion that the window frame tint was an indication of whether you were in a private session or a non-private one, but after some time realised that the tint was merely an effect of what colour the content of the web page happened to be that had been scrolled up behind the title bar. A small thing, but nevertheless misleading. It's also completely arbitrary; what meaning does having a blurry translucent background in a souce list (but not for other window content) actually convey? The whole idea should be canned before it becomes more pervasive. It's already a nuisance and causes numerous graphics glitches (e.g weird black outlines around a non-active progress bar when on a vibrant background). Developers have better things to worry about. The problem is that when these issues were reported (*) just after the first Yosemite seed, the Radar tickets were quickly closed as Behaves as expected. * including the suggestion to not enabled Vibrancy for apps built with previous OS X SDKs. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Blurry is the New Sharp
Well, the user has selected a desktop wallpaper he likes, presumably with a pleasing color scheme. Taking vibrancy from an image the user has already indicated a preference for is much kinder than blurring in whatever happens to be in a window behind the foreground app. — Charles Jenkins On Monday, January 5, 2015 at 7:10 PM, Graham Cox wrote: On 5 Jan 2015, at 11:58 pm, Charles Jenkins cejw...@gmail.com (mailto:cejw...@gmail.com) wrote: if there's a way to tell the window server to use only the desktop image to create vibrancy effects in a the sidebar, ignoring any other windows which may lie between my app and the desktop Would you really want that, even if it could be done? The effect would be that your active window was cutting a hole through the underlying windows to reveal the desktop. As much as the translucency effect is annoying and a performance drag, it is at least consistent with the layered windows metaphor. You'd be better off just making your window entirely opaque, and I think we should be doing that to send Apple the message that we don't want the stinking translucency effect. --Graham ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
UIAutomation, cannot tap UIImagePickerController Choose button
Hi,
I’m trying to make some test with UIAutomation, basically, I select an image
from the camera roll, UIImagePickerController allowsEditing property is set to
YES. When I try to tap the “Choose” button I got this error:
Script threw an uncaught JavaScript error:
target.frontMostApp().windows()[0].buttons()[2] could not be tapped…
Looking at the view hierarchy of UIImagePickerController here’s what I got:
target.frontMostApp().windows()[0].logElementTree();
UIAWindow: rect:{{0, 0}, {320, 568}}
UIANavigationBar: name:Moments rect:{{-320, 0}, {320, 44}}
UIACollectionView: value:page 1 of 1 rect:{{-96, 0}, {320, 568}}
UIAImage: name:UINavigationVerticalColumnShadow.png rect:{{-9,
0}, {9, 568}}
UIAScrollView: rect:{{0, 0}, {320, 568}}
UIAButton: name:Cancel rect:{{13, 514}, {56, 34}}
UIAButton: rect:{{145, 515}, {30, 34}}
UIAButton: name:Choose rect:{{244, 514}, {63, 34}}
So I access the “Choose” button this way:
target.frontMostApp().windows()[0].buttons()[2] and log the view hierarchy:
target.frontMostApp().windows()[0].buttons()[2].logElementTree();
UIAButton: name:Choose rect:{{244, 514}, {63, 34}}
So, definitely is not nil, but when I tap it, I got the error above.
Script threw an uncaught JavaScript error:
target.frontMostApp().windows()[0].buttons()[2] could not be tapped…
Somebody can help me?, UIAutomation is so obscure.
Thank you.
--
Juan Felipe Alvarez Saldarriaga
http://juan.im
Twitter: @nebiros
Google Talk: nebi...@gmail.com
Skype: jfasaldarriaga
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
Re: Blurry is the New Sharp
On Jan 5, 2015, at 12:11 PM, Jens Alfke j...@mooseyard.com mailto:j...@mooseyard.com wrote: I guess the best we can do as developers is to vote with our feet by not adopting it in our apps. The documentation for implementing vibrancy in our own views is incomplete, inconsistent and hard to follow, anyway, and the sample code from WWDC 2014 is confusing and no longer works right on the final release of Yosemite. I spent way too much time trying to make vibrancy work on a relatively complex custom view, and there are still a couple of aspects of it that I can't make work right. But I disagree that vibrancy should be avoided. The few views that were semitransparent in Mavericks and earlier were worse, because I could make out the words showing through the view -- just enough to tempt me to read them. The application switcher (Command-Tab) comes to mind. Now, with vibrancy, there is no longer any temptation to try to read them. -- Bill Cheeseman - b...@cheeseman.name mailto:b...@cheeseman.name ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Blurry is the New Sharp
On Jan 5, 2015, at 1:13 PM, Bill Cheeseman wrote: On Jan 5, 2015, at 12:11 PM, Jens Alfke j...@mooseyard.com mailto:j...@mooseyard.com wrote: I guess the best we can do as developers is to vote with our feet by not adopting it in our apps. The documentation for implementing vibrancy in our own views is incomplete, inconsistent and hard to follow, anyway, and the sample code from WWDC 2014 is confusing and no longer works right on the final release of Yosemite. I spent way too much time trying to make vibrancy work on a relatively complex custom view, and there are still a couple of aspects of it that I can't make work right. But I disagree that vibrancy should be avoided. The few views that were semitransparent in Mavericks and earlier were worse, because I could make out the words showing through the view -- just enough to tempt me to read them. The application switcher (Command-Tab) comes to mind. Now, with vibrancy, there is no longer any temptation to try to read them. Vibrancy gives the same effect we hated years ago, that effect of overblown HDR tonemapped images. The new colors are already eyebleedingly vibrant against more white, resulting in a visually unpleasant UI on iOS and the Mac OS. No idea why the powers that be thought it would be a good idea. It's different for the sake of being different, not different for the sake of being better. Apple's UI direction needs better steering. Much better steering. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Blurry is the New Sharp
I guess the best we can do as developers is to vote with our feet by not adopting it in our apps. (I haven't had to deal with an OS X source list in a while; I assume vibrancy has to be opted into? Or at least there's a way to opt out?) No, it is on by default and no way (that I know of, and I would be very happy to be proven wrong) to opt out. Georg ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Blurry is the New Sharp
Georg, I believe you can uncheck allows vibrancy in IB. But back to my original question: does anyone know how to make the vibrancy effect be based only on the desktop image, ignoring any other windows which might be beneath the foreground app? — Charles On Monday, January 5, 2015 at 13:32, Georg Seifert wrote: No, it is on by default and no way (that I know of, and I would be very happy to be proven wrong) to opt out. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Rearranging NSOutlineView via drag-and-drop
Well, the view-based outline view calls my delegate to get the view pointer for a given item, and in response my delegate dutifully creates one, sets its text and image, and hands it over. But after that the item view I created is owned by the outline view, and I think--but would be happy to be proven wrong--that there no way to ask the outline view to look up that item view pointer for me so I can alter its image. I believe if I wanted to know that pointer at some later time, I'd have to code some way to keep track of it myself. — Charles On Monday, January 5, 2015 at 12:16, Quincey Morris wrote: What does “request a view” mean? ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Rearranging NSOutlineView via drag-and-drop
On Jan 5, 2015, at 12:48 PM, Charles Jenkins cejw...@gmail.com wrote: Well, the view-based outline view calls my delegate to get the view pointer for a given item, and in response my delegate dutifully creates one, sets its text and image, and hands it over. But after that the item view I created is owned by the outline view, and I think--but would be happy to be proven wrong--that there no way to ask the outline view to look up that item view pointer for me so I can alter its image. You're looking for -viewAtColumn:row:makeIfNecessary:. Regards, Ken ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Rearranging NSOutlineView via drag-and-drop
On Jan 5, 2015, at 10:48 , Charles Jenkins cejw...@gmail.com wrote: Well, the view-based outline view calls my delegate to get the view pointer for a given item, and in response my delegate dutifully creates one, sets its text and image, and hands it over. Creating the cell view and populating the cell view are different things, since NSOutlineView re-uses existing view objects for different rows at different times. NSOutlineView calls ‘outlineView:viewForTableColumn:item:’ when it needs to associate a view with a cell. It should be doing this for the views in the rows that you explicitly reloaded. (It would be a horrible bug if it didn’t, obviously. Reloading invalidates *everything* the NSOutlineView thinks it knows about the affected cells.) Thus, it shouldn’t be necessary to *find* the view — you should be doing the reconfiguration in ‘outlineView:viewForTableColumn:item:’. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Rearranging NSOutlineView via drag-and-drop
On Jan 5, 2015, at 10:48 AM, Charles Jenkins cejw...@gmail.com wrote: Well, the view-based outline view calls my delegate to get the view pointer for a given item, and in response my delegate dutifully creates one, sets its text and image, and hands it over. But after that the item view I created is owned by the outline view, and I think--but would be happy to be proven wrong--that there no way to ask the outline view to look up that item view pointer for me so I can alter its image. I believe if I wanted to know that pointer at some later time, I'd have to code some way to keep track of it myself. Use -rowForItem: and -viewAtColumn:row:makeIfNecessary:. But you might also want to file a Radar on -reloadItem: not actually requesting a new view. --Kyle Sluder ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Blurry is the New Sharp
On 05/01/15 19:32, Georg Seifert wrote: I guess the best we can do as developers is to vote with our feet by not adopting it in our apps. (I haven't had to deal with an OS X source list in a while; I assume vibrancy has to be opted into? Or at least there's a way to opt out?) No, it is on by default and no way (that I know of, and I would be very happy to be proven wrong) to opt out. If you are referring to opting out of translucency in the tree/outline view, you can get rid of the effect by setting its background color to nil or something else. I find translucency (which I think is what people really talk about in this thread when mentioning vibrancy) can greatly benefit a UI when applied sensibly but the fact that there is no way to tell tree/outline views to use VIEW background instead of WINDOW background, is, frankly, an outrage. If you want translucent VIEW background on an outline view, you actually need to put the outline in inside a NSVisualEffectsView container. Even though the tree/outline does this automatically, you just don't have any control over it. Regards Markus -- __ Markus Spoettl ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
Re: Rearranging NSOutlineView via drag-and-drop
Thanks to everyone for the info about viewForTableColumn:item:. I overlooked it somehow in my search. You're right, I do all the configuration in outlineView:viewForTableColumn:item:, but when I tested using reloadItem: on affected nodes of the tree, the disclosure triangles got updated but outlineView:viewForTableColumn:item: wasn't called and the images didn't change. I'll try again, though, and set a breakpoint to be sure. I realize it's more likely to be my bug than Apple's. — Charles On Monday, January 5, 2015 at 14:08, Quincey Morris wrote: Thus, it shouldn’t be necessary to *find* the view — you should be doing the reconfiguration in ‘outlineView:viewForTableColumn:item:’. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
