In general, please file a bug report at bugreport.apple.com. For what it’s
worth, I agree, and I don’t think IB should be doing anything at all to try and
guess what constraints we want, or even to keep them consistent. The spirit of
the dev tools is to allow you to do whatever you want (even
I have filed literally hundreds of bug reports. I get the spirit of what you're
saying, but I'm so stressed from this project (and IB's hand in it), and so
demoralized from having my bugs come back as either Duplicate, or Behaves
Correctly, or just stay Open forever, and finally, having to wait
Right, I agree, radarweb’s behaviour is pretty abominable, you can’t see
anything at all going on. But that doesn’t change the fact, making radars is
the only way these things get fixed. I’m glad to hear you’ve reported many
already. Please make more if you can think of unique things that IB
On Mon, Aug 19, 2013, at 09:08 PM, Peter C wrote:
> maximumLineHeight when set to 1.0, the lines is maximum compacted to
> unreadable text. Gradual increase of the value, will see the lines
> expanding. However I discover it to be strange behaviour of
> maximumLineHeight (probably something I don'
On 20/08/2013, at 8:38 AM, Peter C wrote:
> Yes, it is possible to pass values with NSParagraphStyleAttributeName for
> NSString drawInRect:withAttributes. However by default line spacing or gap
> between lines is different compare to CoreText functions (CTFramesetter and
> etc). The gap is t
On 20 Aug, 2013, at 4:09 PM, Kyle Sluder wrote:
> The default line height of Helvetica is 14.0. That information is
> encoded in the font. You can discover this for yourself by asking your
> NSLayoutManager for its defaultLineHeightForFont:. This line height will
> be used for text layout if the
On 20 Aug, 2013, at 4:23 PM, Graham Cox wrote:
> On 20/08/2013, at 8:38 AM, Peter C wrote:
>
>> Yes, it is possible to pass values with NSParagraphStyleAttributeName for
>> NSString drawInRect:withAttributes. However by default line spacing or gap
>> between lines is different compare to Core
On 19 Aug 2013, at 19:18, Alex Zavatone wrote:
> Sent from my iPad
>
> On Aug 18, 2013, at 11:16 AM, "Gerriet M. Denkmann"
> wrote:
>
>> But I do not understand it. CIImage, CGImage, NSImage
>
> I know it's not much, but CI = Core Image, CG = Core Graphics and NS = Next
> Step (Mac). UI I
Trying to convert an older project to Arc, Xcode complains about "Use of
undeclared identifier '_privateDate'".
And threatens that nothing will be done unless I fix this first.
Well - for one: without Arc there are no undeclared identifiers. (Builds
without error or warnings).
The class with pr
You're missing an @synthesize privateData = _privateData; in your
@implementation, would be my guess.
On Aug 20, 2013, at 1:07 PM, Gerriet M. Denkmann wrote:
> Trying to convert an older project to Arc, Xcode complains about "Use of
> undeclared identifier '_privateDate'".
> And threatens that
On 20 Aug 2013, at 19:24, Uli Kusterer wrote:
> You're missing an @synthesize privateData = _privateData; in your
> @implementation, would be my guess.
There is no @synthesize, this is true.
But Xcode normally does not mind, and I think this is (since when?) no longer
necessary (maybe only i
On 20/08/2013, at 9:07 PM, "Gerriet M. Denkmann" wrote:
> How to placate Xcode?
Are you sure it's not the use of retain that it's complaining about? Without
that, your code compiles fine here.
--
Shane Stanley
'AppleScriptObjC Explored'
___
Coc
Sure, but the whole point the OP is trying to make is that the purported error
is being raised by the refactoring process that is _supposed to remove that
retain_. Refactoring would be a very easy process indeed if doing the
conversion yourself is a prerequisite of having Xcode do it.
The use o
On 20 Aug 2013, at 20:27, Fritz Anderson wrote:
> Sure, but the whole point the OP is trying to make is that the purported
> error is being raised by the refactoring process that is _supposed to remove
> that retain_. Refactoring would be a very easy process indeed if doing the
> conversion y
This looks like a bug in Xcode’s refactoring tool — seems it doesn’t understand
the auto-synthesize feature. I would take your test case and attach it to a new
Radar bug report to Apple.
The workaround should be to add an explicit instance variable declaration and
an “@synthesize” directive whe
On 20 Aug 2013, at 21:41, Jens Alfke wrote:
> This looks like a bug in Xcode’s refactoring tool — seems it doesn’t
> understand the auto-synthesize feature. I would take your test case and
> attach it to a new Radar bug report to Apple.
Just done this. Bug 14784266.
Gerriet.
_
On Aug 20, 2013, at 8:43 AM, Gerriet M. Denkmann wrote:
>
> On 20 Aug 2013, at 20:27, Fritz Anderson wrote:
>
>> Sure, but the whole point the OP is trying to make is that the purported
>> error is being raised by the refactoring process that is _supposed to remove
>> that retain_. Refactor
On 20 Aug 2013, at 21:54, glenn andreas wrote:
>
> On Aug 20, 2013, at 8:43 AM, Gerriet M. Denkmann wrote:
>
>>
>> On 20 Aug 2013, at 20:27, Fritz Anderson wrote:
>>
>>> Sure, but the whole point the OP is trying to make is that the purported
>>> error is being raised by the refactoring p
Actually, I think the question is "what version of Xcode are you upgrading the
project from and what version of Xcode are you using to do the conversion?"
That way, it's much easier to pin down the specific case that might be causing
this.
- Alex Zavatone
On Aug 20, 2013, at 10:57 AM, glenn
On Aug 20, 2013, at 12:36 PM, Gerriet M. Denkmann wrote:
> On 19 Aug 2013, at 19:18, Alex Zavatone wrote:
>> Sent from my iPad
>>
>> On Aug 18, 2013, at 11:16 AM, "Gerriet M. Denkmann"
>> wrote:
>>
>>> But I do not understand it. CIImage, CGImage, NSImage
>>
>> I know it's not much, but CI =
On Aug 20, 2013, at 12:36 PM, Gerriet M. Denkmann wrote:
> Well that much I know. And I also know that many NS/UI-things (which use
> Objective-C) often have a CF-counterpart, which uses plain C and often these
> are toll-free bridged. The latter kind is typically used when one needs more
> opt
Hello….
I have a Mac app that is launched via a URL handler that is installed. The
launch services / configuration setup of the URL handler is fine, app launches
just as expected. However, I am seeing an intermittent problem where the URL
handling method:
- (void)handleGetURLEvent:(NSAppleEve
On Aug 20, 2013, at 1:38 PM, Bradley O'Hearne wrote:
> I have a Mac app that is launched via a URL handler that is installed. The
> launch services / configuration setup of the URL handler is fine, app
> launches just as expected. However, I am seeing an intermittent problem where
> the URL han
On 2013 Aug 20, at 11:38, Bradley O'Hearne wrote:
> So far, this problem seems isolated to Snow Leopard, I have not seen it on
> Lion or Mountain Lion. Also, the problem is intermittent [and much more] …
Brad, you probably know more about this problem than anyone in the world today.
For issu
On Aug 20, 2013, at 11:38 AM, Bradley O'Hearne
wrote:
> 1. Is there any guaranteed invocation order of these methods, or is it
> completely random? I cannot think of any scenario where you'd want to process
> the URL launching event *after* the callback which signifies app launch
> completio
If you have code that needs to happen first/once at start, maybe you can try
putting it in awakeFromNib.
Also, I think launching apps via NSWorkspace can be a little more robust than
apple events, when possible.
On Aug 20, 2013, at 3:00 PM, cocoa-dev-requ...@lists.apple.com wrote:
>
> Message
Thanks for the reply, Doug! Sorry, I somehow didn’t notice it had come in
until just now.
I’ll file an ER for suitable API (or for updating the docs, if the conclusion
is not to provide one). Since I’m using NSSpellChecker with my own,
WebView-based content view, I don’t get the benefit of Ap
Dear list,
I have the following structure:
An itemStore object creates a worker object (property of itemStore object) that
hold a weak reference back to the itemStore object;
When the worker classes is done, it sets the itemStore object (of which the
worker class itself is a property) to nil.
On 20 Aug 2013, at 23:32, Diederik Meijer | Ten Horses
wrote:
> Dear list,
>
> I have the following structure:
>
> An itemStore object creates a worker object (property of itemStore object)
> that hold a weak reference back to the itemStore object;
> When the worker classes is done, it sets
On Aug 20, 2013, at 4:32 PM, Diederik Meijer | Ten Horses wrote:
> An itemStore object creates a worker object (property of itemStore object)
> that hold a weak reference back to the itemStore object;
> When the worker classes is done, it sets the itemStore object (of which the
> worker class it
Apologies, no need to respond, I have just fixed this..
Op Aug 20, 2013, om 11:32 PM heeft Diederik Meijer | Ten Horses
het volgende geschreven:
> Dear list,
>
> I have the following structure:
>
> An itemStore object creates a worker object (property of itemStore object)
> that hold a wea
On Aug 20, 2013, at 2:32 PM, Diederik Meijer | Ten Horses wrote:
> Is there any way to NSLog the destruction of the itemStore object?
Sure, but you'll save a lot more time if you use Instruments to track object
lifetimes - it'll show you who does own the object and keeps you from hitting
deall
Wouldn’t be possible to implement dealloc in that class and put an NSLog call
there? Of course, in an ARC project, you wouldn’t call [super dealloc] but
would that cause a problem?
-Laurent.
--
Laurent Daudelin
AIM/iChat/Skype:LaurentDaudelin
http://www.nemesys-
Thanks for this. I'd like to try using the Document object that owns the
itemStore. The itemStore objects are created by the Document object in a loop
as part of a dispatch_async GCD block. The itemStores' workers have a reference
to the Document object. But since the itemStore objects are creat
On 21/08/2013, at 12:59 AM, Gerriet M. Denkmann wrote:
>> What version of Xcode? I just tried this with Xcode 4.6.3 and it worked
>> perfectly.
>
> A difficult question: I am not allowed to talk about this (which might give
> you an idea, which version I was using).
Worked fine for me in an
On Aug 20, 2013, at 12:37 PM, Ken Thomases wrote:
> No, you're mistaken. This is not a callback specifically for an app being
> launched to handle a URL. It's a callback to handle a request to open a URL,
> whenever it happens. It is perfectly normal for it to be delivered after an
> app i
On Aug 20, 2013, at 12:37 PM, Jerry Krinock wrote:
>
> On 2013 Aug 20, at 11:38, Bradley O'Hearne wrote:
>
>> So far, this problem seems isolated to Snow Leopard, I have not seen it on
>> Lion or Mountain Lion. Also, the problem is intermittent [and much more] …
>
> Brad, you probably know
On Aug 20, 2013, at 1:05 PM, Jens Alfke wrote:
>
> On Aug 20, 2013, at 11:38 AM, Bradley O'Hearne
> wrote:
>
>> 1. Is there any guaranteed invocation order of these methods, or is it
>> completely random? I cannot think of any scenario where you'd want to
>> process the URL launching event
Just tested NSParagraphStyle lineHeightMultiple, the line space expands only.
It is similar to NSParagraphStyle lineSpacing, no negative value possible.
Below is the method what I intended to do,
// lspace - 0.0 neutral , negative value the line height contracts and positive
value line height
iOS 6.1.3.
I have a navigation stack in a UIPopover, using autolayout, and I'm
programmtically instantiating a couple of view controllers from scenes in the
storyboard and installing them in a view controller container view in the view
controller on the top of my navigation stack. I swap VCs as
Nevermind, it was a red herring. I thought those views were blocking user
interaction, but it's autolayout sucking ass again, shrinking a parent view
such that it was not encompassing a button in a subview.
On Aug 20, 2013, at 19:12 , Rick Mann wrote:
> iOS 6.1.3.
>
> I have a navigation stac
41 matches
Mail list logo
