> On May 22, 2015, at 8:42 PM, Jens Alfke wrote:
>
> 0xbaddc0dedeadbead
Check Google, or duckduckgo?
It seems to come up in a variety of crashes. I’m not sure that I could pick
Swift out of them, but they pretty exclusively seem to be Yosemite.
> This is obviously a magic value that someone p
On 22 May 2015, at 14:49, Alex Zavatone wrote:
> Thanks for the wake up call, UIi!
I’m sorry. I’d much rather get you the news that you can sleep in :-)
Cheers,
-- Uli Kusterer
“The Witnesses of TeachText are everywhere...”
http://zathras.de
___
Co
I’m trying to debug a mysterious crash in a Swift init method. At the end of
the method there are some calls to objc_release generated by the compiler, and
it’s the first of these that crashes: the object being released has has its
‘isa’ pointer replaced by the value 0xbaddc0dedeadbead. This is
> On 22 May 2015, at 9:51 pm, Jonathan Taylor
> wrote:
>
> I’m trying to think if there is an elegant way of handling the situation I
> find in some of my display code. I have a class which inherits from NSView
> and which overrides drawRect. The class has a number of properties, and if
> th
> On 22 May 2015, at 15:03, Jonathan Taylor
> wrote:
>
> Thanks for your reply Mike:
>
>> Well you could have a single key which you observe internally, and which all
>> the other keys feed into. Whenever it “changes”, treat that as time to mark
>> as needing display. That way you’re asking
On 22 May 2015, at 6:03 am, Jonathan Taylor
wrote:
> I agree that it’s extra indirection, but since performance is never going to
> be an issue, I feel it’s a slight gain on tidiness and maintainability. I
> agree that it’s not a big deal for one property, but when there are lots it
> starts
On 21 May 2015, at 1:33 am, Graham Cox wrote:
> I can’t do a ‘po self’, even just typing it in, at this point, no matter how
> cunning I am at breaking at the right time. It seems as if there really isn’t
> enough info to resolve ‘self’ (the message is "error: use of undeclared
> identifier ‘s
Hi,
I am developing manually a list. After add the view at the main view, only
the first item of the tableView is enabling the selection.
Do someone know about it?
My code:
BoxListaGruposController *boxListaGruposController = [ [
BoxListaGruposController alloc ] init ];
[ boxListaGrupo
Thanks for your reply Mike:
> Well you could have a single key which you observe internally, and which all
> the other keys feed into. Whenever it “changes”, treat that as time to mark
> as needing display. That way you’re asking AppKit to do the work of creating
> all the other observations fo
AHA. I am incorrect.
Now in the office, when reviewing my code in the test, I wasn't testing
auto-synthesis of the properties. Now that I am, I can see that
auto-synthesized properties DO create the ivar with the leading underscore.
Stepping back to my original question, the code that I am re
> On 22 May 2015, at 13:51, Jonathan Taylor
> wrote:
>
> I’m trying to think if there is an elegant way of handling the situation I
> find in some of my display code. I have a class which inherits from NSView
> and which overrides drawRect. The class has a number of properties, and if
> they
I’m trying to think if there is an elegant way of handling the situation I find
in some of my display code. I have a class which inherits from NSView and which
overrides drawRect. The class has a number of properties, and if they change
then the view needs redrawing. At present I have custom set
Using the STKaiti-SC-Black font (display name: Kaiti SC Black) (in TextEdit,
Font Book, or whatever) I get lines like this:
[some app] CoreText: Invalid ‘amor’ Subtable In name = STKaiti-SC-Black, size =
36.00, matrix = 0x0, descriptor = {attributes = {type
= mutable dict, count = 1,
entrie
On May 22, 2015, at 3:43 AM, Uli Kusterer wrote:
> On 21 May 2015, at 19:55, Quincey Morris
> wrote:
>> On May 21, 2015, at 10:40 , Fritz Anderson wrote:
>>>
>>> I must have misinterpreted the question. I had understood Alex wanted a
>>> build option to turn off the auto-synthesis of propert
On 21 May 2015, at 19:55, Quincey Morris
wrote:
> On May 21, 2015, at 10:40 , Fritz Anderson wrote:
>>
>> I must have misinterpreted the question. I had understood Alex wanted a
>> build option to turn off the auto-synthesis of properties, so the compiler
>> could complain at every conflation
15 matches
Mail list logo
