On Nov 11, 2013, at 10:58 PM, Gerriet M. Denkmann wrote:
>
> On 12 Nov 2013, at 09:56, Ken Ferry wrote:
>
>>
>> For more info, please see a talk I gave, <
>> https://deimos.apple.com/WebObjects/Core.woa/BrowsePrivately/adc.apple.com.2233538716.02233538722.2238039498?i=1820509221
>>> .
>
> Th
In my app, we have a couple popovers. The navigation bars in these are black in
iOS 6 (as set in IB). But the black bar looks terrible in iOS 7 (the default
blue tint for elements in the bar is nearly invisible on black, and the corners
bleed through white). So in code, if it’s running in iOS 7,
Well if that is the case, the SVG-to-NSImage (UIImage) code comes to use - just
store always-being-one-pixel lines in SVG as 0-width paths.
On Nov 12, 2013, at 10:22, Seth Willits wrote:
> On Nov 11, 2013, at 4:44 PM, Maxthon Chan wrote:
>
>> What I stumbled upon is that you should use vector
Recently Apple announced that they were going to make past versions of your
apps available to users for download. You had to take special steps to prevent
older versions from being made available. I’m not sure what those are, off the
top of my head, but that might be what’s going on.
Might also
On Nov 11, 2013, at 4:44 PM, Maxthon Chan wrote:
> What I stumbled upon is that you should use vector images in PDF format and
> the system will scale it for you.
Can, may, but not “should.”
Lines that are supposed to be one point wide cannot remain one point wide when
the art is scaled. For
Hi Tom,
I think the problem here is that if you have view A containing textField,
and textField is centered in A, there's no constraint expressing anything
about A's height. A can go to zero height and still have the textField
centered within it.
If you added something giving a height (or fastene
Hey!,
Apple just publish to the App Store an app that I wrote, but seems like is not
the right version, the changes that I push are not there, seems like is the old
version, they publish on the App Store like last Saturday, or Friday, I test
the build that I send to the App Store and it has tho
What I stumbled upon is that you should use vector images in PDF format and the
system will scale it for you.
On Nov 10, 2013, at 16:57, Michael Starke
wrote:
> I did stumble upon the deprecation too, but now am unable to find it again.
> What I do rememeber though is, that NSSegmentStyleTextu
Actually, I bet you called lockFocus on the NSImage in between.
lockFocus is a mutation - you're replacing the original contents of the image
with new drawing. lockFocus will _replace_ your original higher quality art
with new drawing.
See the same talk for more detail.
On Mon, Nov 11,
I dunno, but what comes to mind is stuff like forming a properly-cased title
for a UI element, given a user-typed string. Never trust users to type the
correct case. :)
--
Steve Mills
office: 952-818-3871
home: 952-401-6255
cell: 612-803-6157
On Nov 11, 2013, at 15:27:52, Andy Lee
wrote:
> A
A friend asked why anyone would want the behavior of capitalizedString. The
only thing I could think of was to convert all caps to title case, which seems
an odd scenario to provide API support for.
Is there a more common need for this method that I haven't thought of?
--Andy
Begin forwarded
Hi Mathew,
If you can repro that in a test app, please file it.
The cache is used or tossed at _draw_ time, and it's based on whether the
number of pixels in the area to be covered matches the number of pixels in
the cache.
The -size of the NSImage has only an indirect effect on anything, in tha
On Nov 11, 2013, at 12:09 PM, Kyle Sluder wrote:
> Inset standard doomsday warning that Lion Autosave will not always be optional
Have you got a source for this?
Charles
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admi
On Nov 11, 2013, at 11:59 AM, Kyle Sluder wrote:
> Shorthand for "initializer or one of the methods called by it, like
> -readFromFileWrapper:ofType:".
>
> My point is that it takes a lot of work to subvert NSDocument's understanding
> of when and how a document is loaded, and simply forking o
> On Nov 10, 2013, at 3:57 PM, Charles Srstka wrote:
>
> My app reads complex files that may take up to two minutes to completely
> load. Beachballing while waiting for it is really not an option.
I’m not suggesting you should beachball. I’m suggesting you adopt
+canConcurrentlyReadFilesOfTyp
> On Nov 10, 2013, at 9:37 PM, Seth Willits wrote:
>
> On Nov 10, 2013, at 1:14 PM, Kyle Sluder wrote:
>
>>> On Nov 10, 2013, at 1:06 PM, Charles Srstka
>>> wrote:
>>>
>>> What I usually do is just have NSDocument's
>>> readFromData/URL/fileWrapper/etc method not actually do much, and then
On Nov 7, 2013, at 10:10 AM, Mike Abdullah wrote:
> Ah, that’s a shame.
>
> Come to think of it, there’s a limit on how many security-scoped bookmarks
> you’re allowed to access at once. I wonder, does the problem seem to happen
> around a particular, fairly predictable, number of bookmarks?
17 matches
Mail list logo
