Is it something that broke in 10.10.3?
Apparently, it used to work in earlier version.
-Original Message-
From: cocoa-dev-bounces+saarora=quark@lists.apple.com
[mailto:cocoa-dev-bounces+saarora=quark@lists.apple.com] On Behalf Of
Gordon Apple
Sent: Friday, May 08, 2015 1:54 AM
To
> On May 7, 2015, at 9:43 PM, Michael David Crawford
> wrote:
>
> Another way would be for me to render the entire view in an offscreen
> image buffer, which I expect I could do far more efficiently than by
> making many calls into UIRectFill or even CoreGraphics.
Actually, no. Rendering in so
> On May 7, 2015, at 9:43 PM, Michael David Crawford
> wrote:
>
> If I autorotate, redrawing the vertical lines takes hundreds
> of times as long as redrawing the horizontal lines. That makes sense
> as one can draw a horizontal line by incrementing a pointer into the
> image buffer. To draw
> On 8 May 2015, at 2:43 pm, Michael David Crawford
> wrote:
>
> My iOS app enables the user to toggle on and off a square grid. When
> the grid is enabled, a tap inside a cell toggles the color of the cell
> between black and blue. When the grid is disabled, one can use a
> pinch-zoom gestur
My iOS app enables the user to toggle on and off a square grid. When
the grid is enabled, a tap inside a cell toggles the color of the cell
between black and blue. When the grid is disabled, one can use a
pinch-zoom gesture to adjust the sizes of the cells.
(I'm not so sure that's a sensible UI
> On 8 May 2015, at 6:11 am, Jerry Krinock wrote:
>
> I would like to subclass NSSlider to make it work like the "volume control"
> on a mid 19th-century radio receiver. That is, I want the minimum value to be
> at 7 o'clock, and the maximum value to be at 5 o'clock.
Jerry,
Since I found t
Thanks!
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 Thu, May 7, 2015 at 4:24 PM, Graham Cox wrote:
>
>> On 8 May 2015, at 9:04 am, Michael David Crawfor
> On 8 May 2015, at 9:04 am, Michael David Crawford
> wrote:
>
> Then draw the indicator with an image from a PNG
I usually use PDF, because then you get scalable graphics without having to
worry about 2x, 3x screens and so on. Any slower performance is usually
unnoticeable for simple graph
If you draw your own control, it might help you to get started to make
a very rough drawing of the control, one with no moving parts but with
the areas of the control clearly delineated so you know where to do
your hit-testing. Then draw your indicator with a black circle or
square. Then draw the
> On 8 May 2015, at 6:11 am, Jerry Krinock wrote:
>
> a mid 19th-century radio receiver
Really Jerry? Radio receivers weren’t a thing until the 1920s!
> Am I correct that the answer is "no"? Keep in mind that we're not just
> drawing here; this is a control; we need mouse clicks, etc.
>
>
You could do what Apple's UIKit engineers do: implement your own
subclass of UIView, with your own drawing and hit testing. Then you
could put your radio in a wooden cabinet, maybe model some of the warm
distortion that vacuum tubes yield
Michael David Crawford, Consulting Software Engineer
mdcraw
In iOS I have used the “transform” property of UIView to rotate a slider.
David
> On May 7, 2015, at 1:11 PM, Jerry Krinock wrote:
>
> I would like to subclass NSSlider to make it work like the "volume control"
> on a mid 19th-century radio receiver. That is, I want the minimum value to be
>
I would like to subclass NSSlider to make it work like the "volume control" on
a mid 19th-century radio receiver. That is, I want the minimum value to be at 7
o'clock, and the maximum value to be at 5 o'clock. There two issues in using
the circular version of NSSlider for this:
1. There is no
Apparently so. I have had difficulty dragging things into an open
(non-transient) popover. It just doesn¹t work.
On 5/7/15 1:00 PM, "cocoa-dev-requ...@lists.apple.com"
wrote:
> I am trying to drag a NSTableView row on to a NSView on the same window. But
> the window is a non-key window (made exp
On May 7, 2015, at 6:44 AM, Daniel Höpfl wrote:
>
> I'd change the code as follows:
>
> // init
> self.cycler = [[[GridCycler alloc] initWithGrid: self] autorelease];
>
> // alternative init, if you want to bypass the autorelease pool:
>
> GridCycler *cycler = [[GridCycler alloc] initWithGrid:
When using auto layout with a scroll view, you would want at least constraints
to fix the position of the document view within the clip view. Usually, you
fix it to the top-left.
If the document view should re-flow its content to fit the width of the clip
view, like a text view or collection v
On Thu, May 7, 2015, at 10:52 AM, Jens Alfke wrote:
>
> > On May 6, 2015, at 9:10 PM, Luther Baker wrote:
> >
> > I'm probably missing something ... but fundamentally, the whole point of
> > constraints between the scrollview and its children is so that the
> > scrollview knows how big to make
> On May 6, 2015, at 9:10 PM, Luther Baker wrote:
>
> I'm probably missing something ... but fundamentally, the whole point of
> constraints between the scrollview and its children is so that the scrollview
> knows how big to make its contentSize. It sounds like you've got this flipped
> ...
On Thu, 7 May 2015 10:57:05 -0400, Michael Swan said:
>On OS X NSPersistentDocument can only make flat files, not packages like
>UIManagedDocument (I've filed a bug about there being no counterpart to
>UIManagedDocument for OS X, been open for over a year now…).
Only a year? Mine's been open for
Dave,
Unfortunately on the OS X side with iCloud, Core Data, and documents it is
pretty much a pick any two situation. The iOS side can be done but there are
some gotchas not really covered in the documentation. I've actually just
started work on my own custom subclasses of UIManagedDocument and
I am trying to drag a NSTableView row on to a NSView on the same window. But
the window is a non-key window (made explicitly).
Some times after I receive " - draggingEntered: " message, no other message
comes.
If I make the window as a keywindow, works perfectly.
Does the NSView Drag Protocol
Hi,
Expanding the "potential leak" message yields:
Static analyser is right, there is a potential leak.
Based on what Aaron said, assume the following usage of your class:
LifeGrid *grid = [[LifeGrid alloc] init];
// GridCycler is allocated (retain count: +1)
// GridCycler is retained by pro
22 matches
Mail list logo
