January 2011 - Cocoa-dev - lists.apple.com

Re: text orientation/positioning with layout manager
by Aki Inoue 31 Jan '11

31 Jan '11

site_archiver(a)lists.apple.com Delivered-To: Cocoa-dev(a)lists.apple.com The precise definition of the point specified by the argument is the top left corner of the text container containing the glyph range in the focused view coordinate system. Aki On Jan 31, 2011, at 3:18 PM, Graham Cox wrote: > > On 01/02/2011, at 9:09 AM, Todd Heberlein wrote: > >> I'm doing a simple experiment using NSTextStorage, NSLayoutManager, NSTextContainer to draw some text (I am basing this on the CircleView example because I want some of that orientation power later). >> >> I have found that when rendering the text using drawGlyphsForGlyphRange:atPoint:, I don't get the text where I expected. It is higher than I expect. Furthermore, when I draw a rectangle around the text (or try to) using the rectangle from usedRectForTextContainer:, the text is outside the rectangle (in short, the rectangle is where I expect it to be, but the text glyphs are not). >> >> Is there a secret incantation that I am missing? > > > One thing that caught me out at first was that text is laid out based on the top, left of the glyph's bounding box, not on some notional baseline. The glyphs are positioned so that the baselines line up, but this is done by offsetting the top edge of the bbox. So if you assume that it's the baseline you're setting, text will be placed generally higher than expected. Is that what's happening? > > --Graham > > > _______________________________________________ > > Cocoa-dev mailing list (Cocoa-dev(a)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: > http://lists.apple.com/mailman/options/cocoa-dev/aki%40apple.com > > This email sent to aki(a)apple.com _______________________________________________ Cocoa-dev mailing list (Cocoa-dev(a)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: http://lists.apple.com/mailman/options/cocoa-dev/site_archiver%40lists.appl… This email sent to site_archiver(a)lists.apple.com

1 0

Re: text orientation/positioning with layout manager
by Graham Cox 31 Jan '11

31 Jan '11

site_archiver(a)lists.apple.com Delivered-To: Cocoa-dev(a)lists.apple.com On 01/02/2011, at 9:09 AM, Todd Heberlein wrote: > I'm doing a simple experiment using NSTextStorage, NSLayoutManager, NSTextContainer to draw some text (I am basing this on the CircleView example because I want some of that orientation power later). > > I have found that when rendering the text using drawGlyphsForGlyphRange:atPoint:, I don't get the text where I expected. It is higher than I expect. Furthermore, when I draw a rectangle around the text (or try to) using the rectangle from usedRectForTextContainer:, the text is outside the rectangle (in short, the rectangle is where I expect it to be, but the text glyphs are not). > > Is there a secret incantation that I am missing? One thing that caught me out at first was that text is laid out based on the top, left of the glyph's bounding box, not on some notional baseline. The glyphs are positioned so that the baselines line up, but this is done by offsetting the top edge of the bbox. So if you assume that it's the baseline you're setting, text will be placed generally higher than expected. Is that what's happening? --Graham _______________________________________________ Cocoa-dev mailing list (Cocoa-dev(a)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: http://lists.apple.com/mailman/options/cocoa-dev/site_archiver%40lists.appl… This email sent to site_archiver(a)lists.apple.com

1 0

worker thread iterating over array - SLOW
by Peter Lübke 31 Jan '11

31 Jan '11

site_archiver(a)lists.apple.com Delivered-To: cocoa-dev(a)lists.apple.com Hi list, - Peter _______________________________________________ Cocoa-dev mailing list (Cocoa-dev(a)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: http://lists.apple.com/mailman/options/cocoa-dev/site_archiver%40lists.appl… I use a worker thread in my app that invokes the same method(s) on all objects in an array sent from the main thread. The array may contain thousands of objects. The main thread communicates with the worker thread via distributed objects. Everything works fine except performance is too slow. Seems to me that my NSConnection asks for the method signature each time the method is invoked on an object in the array, thus adding massive overhead. The shared objects approach - call NSThread's - detachNewThreadSelector:toTarget:withObject: with the array as argument 3, have the secondary thread do the job and exit - is way faster! I just started using DO and probably missed more than one thing, so any help is very much appreciated. This email sent to site_archiver(a)lists.apple.com

1 0

Re: Main menu in NSDocument based application
by Bruce Cresanta 31 Jan '11

31 Jan '11

site_archiver(a)lists.apple.com Delivered-To: cocoa-dev(a)lists.apple.com Thank you, I needed to know about the responder chain... The thing is well thought out. Bruce On Jan 31, 2011, at 3:43 PM, Sherm Pendley wrote: > On Mon, Jan 31, 2011 at 5:25 PM, Bruce Cresanta <cresanta(a)me.com> wrote: >> >> I've been scouring through the docs trying to figure out how to get a reference to the main menu in an NSDocument based app. I need to make programmatic changes to the menu depending on which NSDocument is key. Would you please help me find a pointer to the main menu? > > What kind of changes? In general, adding and removing menu items is > discouraged in Mac apps. Disabling menu items that don't apply to the > current document and/or selection is the preferred approach, and for > that you don't need a pointer to the menu. The current document is in > the responder chain, so if it doesn't respond to a menu item's action > message, that menu item will be disabled automatically. For more > detailed control, for example to disable a menu item based on the > current selection in a document, one can write a -validateMenuItem: > method to decide whether the given menu item should be enabled or not. > > I'm not trying to give you the "HIG lecture," I'm just saying - > depending on what you want to do, there might be an easier way to do > it that doesn't actually need a pointer to the main menu. On the other > hand, there are certainly reasons to alter the main menu in other ways > that *do* require such a pointer. So, if you do need it, there's > NSApplications's mainMenu method, which you can call using the NSApp > global, as in: > > NSMenu *menu = [NSApp mainMenu]; > > sherm-- > > -- > Cocoa programming in Perl: > http://camelbones.sourceforge.net _______________________________________________ Cocoa-dev mailing list (Cocoa-dev(a)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: http://lists.apple.com/mailman/options/cocoa-dev/site_archiver%40lists.appl… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Main menu in NSDocument based application
by Sherm Pendley 31 Jan '11

31 Jan '11

site_archiver(a)lists.apple.com Delivered-To: cocoa-dev(a)lists.apple.com Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=V0oKj/wSG9xrG/VFMzuEyY5/hmJq0l6/64R0NkHiz4g=; b=x1UL1LPU8RhXqhah5WwZQgw/qK1SDN+UzH+ne8Xpc/RI/8mvvNg2GuK1IRwUxLMU7u O/ceQnS28rIqhj37FRQ8tR3zrdJxfFWCU2j3fc2WDb74RiDCz7O2QCVE5QNIupamYufA XshFuZ7Z8lobL/u7IYmu0e7BKqiE+CyvXdXNo= Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=mN+QZtdEeos+kIZv7OzNeI2wykDmkyn75yCNwOfESZTl4tehS142SirrsYaNULKIkq KXsHWqJzESdtkGR1t8dv6h9iXz6L5Ho4nQlUS0VghexSFpf6k9lUGKhOtUk+P1klpguy 4ra8XUPBpvsSc5WW85inuolSYi25BSOkdsKe0= On Mon, Jan 31, 2011 at 5:25 PM, Bruce Cresanta <cresanta(a)me.com> wrote: > > I've been scouring through the docs trying to figure out how to get a reference to the main menu in an NSDocument based app. I need to make programmatic changes to the menu depending on which NSDocument is key. Would you please help me find a pointer to the main menu? What kind of changes? In general, adding and removing menu items is discouraged in Mac apps. Disabling menu items that don't apply to the current document and/or selection is the preferred approach, and for that you don't need a pointer to the menu. The current document is in the responder chain, so if it doesn't respond to a menu item's action message, that menu item will be disabled automatically. For more detailed control, for example to disable a menu item based on the current selection in a document, one can write a -validateMenuItem: method to decide whether the given menu item should be enabled or not. I'm not trying to give you the "HIG lecture," I'm just saying - depending on what you want to do, there might be an easier way to do it that doesn't actually need a pointer to the main menu. On the other hand, there are certainly reasons to alter the main menu in other ways that *do* require such a pointer. So, if you do need it, there's NSApplications's mainMenu method, which you can call using the NSApp global, as in: NSMenu *menu = [NSApp mainMenu]; sherm-- -- Cocoa programming in Perl: http://camelbones.sourceforge.net _______________________________________________ Cocoa-dev mailing list (Cocoa-dev(a)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: http://lists.apple.com/mailman/options/cocoa-dev/site_archiver%40lists.appl… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Main menu in NSDocument based application
by Lee Ann Rucker 31 Jan '11

31 Jan '11

site_archiver(a)lists.apple.com Delivered-To: cocoa-dev(a)lists.apple.com Thread-index: AcvBmEet9z5aMQ5zTEa8umfz7mpaew== Thread-topic: Main menu in NSDocument based application On Jan 31, 2011, at 2:25 PM, Bruce Cresanta wrote: > Hello, > > I've been scouring through the docs trying to figure out how to get a reference to the main menu in an NSDocument based app. I need to make programmatic changes to the menu depending on which NSDocument is key. Would you please help me find a pointer to the main menu? NSDocument validateUserInterfaceItem: will probably give you everything you need. There's seldom a need to update a menu before it asks to be updated. If you find you must use the main menu, the method you need is conveniently named mainMenu. One of my favorite tricks for finding new things is to set XCode's documentation search mode to "prefix" and type something likely._______________________________________________ Cocoa-dev mailing list (Cocoa-dev(a)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: http://lists.apple.com/mailman/options/cocoa-dev/site_archiver%40lists.appl… This email sent to site_archiver(a)lists.apple.com

1 0

Main menu in NSDocument based application
by Bruce Cresanta 31 Jan '11

31 Jan '11

site_archiver(a)lists.apple.com Delivered-To: cocoa-dev(a)lists.apple.com Hello, I've been scouring through the docs trying to figure out how to get a reference to the main menu in an NSDocument based app. I need to make programmatic changes to the menu depending on which NSDocument is key. Would you please help me find a pointer to the main menu? Thank you, Bruce _______________________________________________ Cocoa-dev mailing list (Cocoa-dev(a)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: http://lists.apple.com/mailman/options/cocoa-dev/site_archiver%40lists.appl… This email sent to site_archiver(a)lists.apple.com

1 0

Re: text orientation/positioning with layout manager
by Douglas Davidson 31 Jan '11

31 Jan '11

site_archiver(a)lists.apple.com Delivered-To: Cocoa-dev(a)lists.apple.com The layout manager expects to be drawing within a flipped context. Douglas Davidson On Jan 31, 2011, at 2:09 PM, Todd Heberlein wrote: > I'm doing a simple experiment using NSTextStorage, NSLayoutManager, NSTextContainer to draw some text (I am basing this on the CircleView example because I want some of that orientation power later). > > I have found that when rendering the text using drawGlyphsForGlyphRange:atPoint:, I don't get the text where I expected. It is higher than I expect. Furthermore, when I draw a rectangle around the text (or try to) using the rectangle from usedRectForTextContainer:, the text is outside the rectangle (in short, the rectangle is where I expect it to be, but the text glyphs are not). > > Is there a secret incantation that I am missing? > > Thanks, > > Todd > > Basic code snippet: > > point = NSMakePoint(1.0, 1.0); > glyphRange = [layoutManager glyphRangeForTextContainer:textContainer]; > usedRect = [layoutManager usedRectForTextContainer:textContainer]; > usedRect.origin = point; > > [layoutManager drawGlyphsForGlyphRange:glyphRange atPoint:point]; > [[NSBezierPath bezierPathWithRect: rect] stroke]; > _______________________________________________ > > Cocoa-dev mailing list (Cocoa-dev(a)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: > http://lists.apple.com/mailman/options/cocoa-dev/ddavidso%40apple.com > > This email sent to ddavidso(a)apple.com _______________________________________________ Cocoa-dev mailing list (Cocoa-dev(a)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: http://lists.apple.com/mailman/options/cocoa-dev/site_archiver%40lists.appl… This email sent to site_archiver(a)lists.apple.com

1 0

text orientation/positioning with layout manager
by Todd Heberlein 31 Jan '11

31 Jan '11

site_archiver(a)lists.apple.com Delivered-To: Cocoa-dev(a)lists.apple.com I'm doing a simple experiment using NSTextStorage, NSLayoutManager, NSTextContainer to draw some text (I am basing this on the CircleView example because I want some of that orientation power later). I have found that when rendering the text using drawGlyphsForGlyphRange:atPoint:, I don't get the text where I expected. It is higher than I expect. Furthermore, when I draw a rectangle around the text (or try to) using the rectangle from usedRectForTextContainer:, the text is outside the rectangle (in short, the rectangle is where I expect it to be, but the text glyphs are not). Is there a secret incantation that I am missing? Thanks, Todd Basic code snippet: point = NSMakePoint(1.0, 1.0); glyphRange = [layoutManager glyphRangeForTextContainer:textContainer]; usedRect = [layoutManager usedRectForTextContainer:textContainer]; usedRect.origin = point; [layoutManager drawGlyphsForGlyphRange:glyphRange atPoint:point]; [[NSBezierPath bezierPathWithRect: rect] stroke]; _______________________________________________ Cocoa-dev mailing list (Cocoa-dev(a)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: http://lists.apple.com/mailman/options/cocoa-dev/site_archiver%40lists.appl… This email sent to site_archiver(a)lists.apple.com

1 0

Re: Help Book authoring tool?
by Jerry Krinock 31 Jan '11

31 Jan '11

site_archiver(a)lists.apple.com Delivered-To: cocoa-dev(a)lists.apple.com You should look at some of the solutions which have been suggested, and try *really hard* to accept them as they are, or with minor modifications if they are open-sourced. Unfortunately, I was unable to do so, and succumbed to the temptation to roll my own, as others have done. It works great, I enjoy writing Perl, and I love it, but it used up two weeks of my life that could better have been spent writing Cocoa code. _______________________________________________ Cocoa-dev mailing list (Cocoa-dev(a)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: http://lists.apple.com/mailman/options/cocoa-dev/site_archiver%40lists.appl… This email sent to site_archiver(a)lists.apple.com

1 0