Re: How to support larger NSView hierarchy?

On Feb 27, 2012, at 20:46 , Graham Cox wrote: > Jeez. Indeed. Especially as it's usually taken as a given that large numbers of NSViews aren't going to perform well. Trying to make the scenario work might be quixotic at best. However, two thoughts did spring to mind: 1. It might be easier (an

Re: Round corners of borderless NSWindow without set it transparent

On Feb 27, 2012, at 5:45 AM, Andrea3000 wrote: > Then, if I set my NSWindow non-opaque I correctly get rounded corners but the > window becomes very slow expecially during resize. Mmm…. that doesn't sound right. You shouldn't notice anything being slow. > Therefore I'm looking for a way to m

Re: How to support larger NSView hierarchy?

Jeez. Perhaps it would be better to explain your goals, rather than fragments of an implementation that appears to be, on the face of it, pointless. In a scroll view, views that are fully clipped out by the clip view, and those which do not intersect the dirty rects, are simply not drawn. At al

How to support larger NSView hierarchy?

In my implementation, I know enough about my very large NSView hierarchy that allows me to clip and draw the visible hierarchy very quickly. If there was a faster way to getRectsBeingDrawn for an entire view hierarchy in an offscreen window, and then reset NSWindow dirty rects needing display man

Round corners of borderless NSWindow without set it transparent

I'm trying to round edges of a borderless NSWindow without having to mark it as transparent with setOpaque:NO. My testbed is made only of a borderless NSWindow, its Content View and a regular NSView. The NSView is subclassed to override drawRect method in order to round corners of the view. Th

Re: Application Suite Preferences

On Feb 27, 2012, at 2:24 AM, Bill Cheeseman wrote: >> At any rate, I'm interested in hearing the thoughts of anyone who really >> knows how these suite preferences should be used. > > My UI Actions product does it exactly the > way you describe, in every parti

Accelerate/vDSP.h question

Have the vDSP functions vDSP_vabs and vDSP_vabsD recently changed? They seem to be no longer working other than to simply return an unchanged version of an input. Here is a simple, Cocoa test routine I used to prove the point: unsigned intii; double aa[10], bb[10];

Re: sudden errors

On Feb 27, 2012, at 4:53 PM, H. Miersch wrote: > > On 27. Feb 2012, at 23:01, H. Miersch wrote: > >> hi. >> my project used to build OK, until today. now xcode keeps throwing errors >> like this at me: >> >> Unknown type name 'ViewManager' >> >> yes, i import ViewManager.h, and no, i did

Re: sudden errors

On 27. Feb 2012, at 23:01, H. Miersch wrote: > hi. > my project used to build OK, until today. now xcode keeps throwing errors > like this at me: > > Unknown type name 'ViewManager' > > yes, i import ViewManager.h, and no, i didn't change any declarations. is > this a bug in Xcode? >

sudden errors

hi. my project used to build OK, until today. now xcode keeps throwing errors like this at me: Unknown type name 'ViewManager' yes, i import ViewManager.h, and no, i didn't change any declarations. is this a bug in Xcode? like i said, until sometime today this used to build ok. what a

Re: Was: issues using encodeWithCoder: with NSAttributedString for iOS

On Feb 27, 2012, at 3:11 AM, Gregory Weston wrote: >> I don’t know of an easy workaround. Back in the day I would have suggested >> creating a category on CGColor that adds the required archiving methods, but >> doing this will get you rejected from the App Store. > > Wait, what? Where's that

Re: Recommended way to present a font preference

On Feb 26, 2012, at 8:13 PM, John Brownie wrote: > I'm rewriting an existing Carbon application with Cocoa, and am working on > the preferences. One preference that the user should be able to set is a > default font and size for text display. In the Carbon app, there is a pop-up > button with a

advice for new project with resizing views

Hi, I need to work on a project where the main window is a view that accepts drops, and after the drop is complete the window will expand/resize to reveal a table view where I will show the needed data. An example would be this old appzapper app that's the first that comes to mind. I have not

Re: Was: issues using encodeWithCoder: with NSAttributedString for iOS

On 27.02.2012, at 12:11, Gregory Weston wrote: > Jens Alfke wrote: > >> I don’t know of an easy workaround. Back in the day I would have suggested >> creating a category on CGColor that adds the required archiving methods, but >> doing this will get you rejected from the App Store. > > Wait, wh

Was: issues using encodeWithCoder: with NSAttributedString for iOS

Jens Alfke wrote: > I don’t know of an easy workaround. Back in the day I would have suggested > creating a category on CGColor that adds the required archiving methods, but > doing this will get you rejected from the App Store. Wait, what? Where's that documented? I haven't tried submitting so

Re: Application Suite Preferences

On Feb 27, 2012, at 2:06 AM, Seth Willits wrote: > At any rate, I'm interested in hearing the thoughts of anyone who really > knows how these suite preferences should be used. My UI Actions product does it exactly the way you describe, in every particular. I

Re: [Obj-C] if (self) vs. if (self != nil)

On 27 Feb 2012, at 03:51, Preston Sumner wrote: > On Feb 26, 2012, at 7:38 PM, Graham Cox wrote: > >> >> On 27/02/2012, at 1:27 PM, Karl Goiser wrote: >> >>> use double parentheses >> >> >> Yes, but that's not what the poster was suggesting. I pointed out why that >> form is bad. >> >> This

Re: [Obj-C] if (self) vs. if (self != nil)

Le 27 févr. 2012 à 02:40, Graham Cox a écrit : > > On 27/02/2012, at 12:13 PM, William Squires wrote: > >> I prefer the "if (self = [super init])" combined form, myself. > > > One potentially annoying thing about this form is that, if you compile with > plenty of warnings on, such as the pos

Bug in 10.6 NSPasteboard API? (was: 10.6 NSPasteboard API mixes up types?)

I am still very much puzzled by the issue I described below, so I still hope to find a taker for it. While the OS 10.5 API cleanly separated pasteboard types, the 10.6 API converts NSURL data to strings and adds it to any existing string data - i.e. when pasting the data into e.g. a text view i

Re: issues using encodeWithCoder: with NSAttributedString for iOS

A very naïve suggestion is that if you are targeting OS X you might be able to use HTML or RTF. Save that and convert the stored into to an attributed string at run time. One idea of font descriptors is that a particular font may not exist on a particular computer, but similar ones might be avail