On Jan 26, 2015, at 23:32 , Jerry Krinock wrote:
>
> You seem to be saying that the only example given by Apple is a bad example,
> because it is a a nontypical, special case. I mean, most attributes in most
> apps are objects, not scalars.
I’m not sure that it’s “bad”, though it is nontypic
Hi Gordon,
Thanks for the heading up. It worked.
On Mon, Jan 26, 2015 at 11:23 PM, Gordon Apple wrote:
> You can stack views and controls however you like. I do it all the time. You
> need to pay attention to the list of views, not just the visuals in iB. Just
> use an outlet or binding to hide
I have a multi-column table that I am converting from an ObjC/cell-based
implementation to a Swift/view-based implementation. The cells are text, so I
am now using a vanilla text-only NSTableCellView in each column.
When the application launches, I can shrink the columns just fine — the text
sh
> What in the world is that nonCompliantKVCivar? I tried it in my project, on
> the ‘rating’ property as in my YouTube video.
>
> - (void)setPrimitiveRating:(NSNumber*)newRating {
>rating = newRating ;
> }
>
> Does not compile. The compiler never heard of ‘rating’. Same result if I
> cha
> On 2015 Jan 27, at 01:24, Quincey Morris
> wrote:
>
> I’m not sure that it’s “bad”, though it is nontypical, which is why there’s a
> [nontypical] custom accessor. a Core Data property access has two general
> steps … you can customize one or both of these steps.
OK, the documentation writ
On Jan 27, 2015, at 7:32 AM, Thomas Wetmore wrote:
> I have a multi-column table that I am converting from an ObjC/cell-based
> implementation to a Swift/view-based implementation. The cells are text, so I
> am now using a vanilla text-only NSTableCellView in each column.
>
> When the applicat
> On 27 Jan 2015, at 22:32, Thomas Wetmore wrote:
> There must be a constraint problem, and I have been playing around with them
> for awhile, but no joy yet. Googling has not turned up a similar issue. I
> would have assumed that when I dragged the NSTableCellView into the
> NSTableColumn usi
I have the XIB set for auto layout. However, after dragging an NSTableCellView
into the NSTableHeader, IB’s size inspector (for the table cell view) reports
that there are no constraints on the cell view. This is clearly the issue.
Since I am learning Swift, cell-based views, and auto-layout all
> On Jan 27, 2015, at 10:48 AM, Roland King wrote:
>
>
>> On 27 Jan 2015, at 22:32, Thomas Wetmore wrote:
>> There must be a constraint problem, and I have been playing around with them
>> for awhile, but no joy yet. Googling has not turned up a similar issue. I
>> would have assumed that wh
>>
>> None of the above I’d expect. What constraints are there between the text
>> view and the cell which contains it? I don’t remember there being any by
>> default, which means at runtime some would be implicitly added, probably a
>> fixed position and fixed width constraint if you hadn’
> On 2015 Jan 27, at 06:46, Keary Suska wrote:
>
> Better, however, to have a property declaration, which would also synthesize
> an ivar in modern LLVMs (as of Xcode 5?).
You mean the property declaration would synthesize the ivar. I didn’t try
that. I agree it would be better.
>> It stil
On Jan 27, 2015, at 10:48:29, Roland King wrote:
>
>>
>> Using IB to check the constraints on the NSTextField within the
>> NSTableCellView, IB states: “The selected views have no constraints. At
>> build time, explicit left, top, width, and height constraints will be
>> generated for the vie
My app uses this call, and it worked fine until I sandboxed it. The
documentation for this call says:
> For sandboxed apps in OS X, the current home directory is not the same as the
> user’s home directory. For a sandboxed app, the home directory is the app’s
> home directory. So if you specifi
> On Jan 27, 2015, at 12:06 PM, Steve Mills wrote:
>
> On Jan 27, 2015, at 10:48:29, Roland King wrote:
>>
>>>
>>> Using IB to check the constraints on the NSTextField within the
>>> NSTableCellView, IB states: “The selected views have no constraints. At
>>> build time, explicit left, top,
> On Jan 27, 2015, at 2:24 AM, Quincey Morris
> wrote:
>
> Clearly, all this customization takes some coordination between steps 1 and
> 2, even if it’s just to know which of them needs to be customized in any
> particular case, and how. That where the documentation falls down — it gives
> r
On Tue, Jan 27, 2015, at 12:21 PM, Richard Charles wrote:
> You can’t override a primitive accessor because one is dynamically
> generated for you at runtime if it is needed. If a custom primitive
> accessor is implemented then the managed object subclass must provide an
> ivar for backing storage.
Hello, all. It has been long time for me to write anything in this mailing
list, but I prefer this than web based one Apple now pushes.
Anyway.. I have some issue with “Window list”
If a window is created, it’s added to a window list under the “Window” menu and
its equivalent counter part on th
> On Jan 27, 2015, at 9:20 AM, Jon Baumgartner
> wrote:
>
> So how do I get /Users//file.txt to output as ~/file.txt when
> my app is sandboxed?
Why do you need it to? That’s not the kind of path you should be displaying in
the UI, because it won’t make sense to anyone but geeks. Is this a
> On Jan 27, 2015, at 11:28 AM, Kyle Sluder wrote:
>
> Historically, I've not been a big Core Data user, but does
> -[NSManagedObject setPrimitiveValue:forKey:] not do what you want?
That is a key-value coding method. If I remember correctly, key-value coding
does not bypass existing accessor
Yeah. The app is specifically for copying paths, and applying various
transformations to the path. Developers use it but also general users.
On January 27, 2015 at 2:03:46 PM EST, Jens Alfke wrote:On
Jan 27, 2015, at 9:20 AM, Jon Baumgartner
wrote: So how do I get /Users//file.txt to output
On Tue, Jan 27, 2015, at 01:06 PM, Richard Charles wrote:
>
> > On Jan 27, 2015, at 11:28 AM, Kyle Sluder wrote:
> >
> > Historically, I've not been a big Core Data user, but does
> > -[NSManagedObject setPrimitiveValue:forKey:] not do what you want?
>
> That is a key-value coding method.
No i
On Jan 27, 2015, at 11:06 , Richard Charles wrote:
>
> That is a key-value coding method.
It’s not, as Kyle just said.
FWIW, there is yet another way to get to backing store from a custom primitive
accessor — define another, private, Core Data property, and use *its* primitive
accessors. Thi
You guess correctly. It's a very large subject, and a mailing list is no place
for a tutorial, but here's a direction:
Do not learn auto layout as if you has a gun to your head. Do not rush. Do not
poke constraints in one-by-one until they seem to be working; it'll take hours
to dig yourself ou
On Jan 27, 2015, at 9:52 AM, Jerry Krinock wrote:
>
>> On 2015 Jan 27, at 06:46, Keary Suska wrote:
>>
>> Better, however, to have a property declaration, which would also synthesize
>> an ivar in modern LLVMs (as of Xcode 5?).
>
> You mean the property declaration would synthesize the ivar.
> On 2015 Jan 27, at 10:38, JongAm Park wrote:
>
> I searched Apple’s documents, but there looks to be no explicit way to
> remove/add window list.
I don’t think there is. If the app is using the Cocoa frameworks and has an
NSApplication (NSApp), you would do this by implementing -applicatio
-[NSApplicationDelegate applicationDockMenu:]
You can customize everything except the recent documents; you get that for free
and can't get rid of it - no, not even if the user clears recent documents from
the main menu.
On Jan 27, 2015, at 10:38 AM, JongAm Park wrote:
> Hello, all. It has be
On Jan 27, 2015, at 12:44 , Keary Suska wrote:
>
> That part of the conversation was private between you and Quincey. I am
> simply curious as I can't imagine why one would want to.
It wasn’t intentionally private. It was just one of those cases where a post
with a lot of invisible formatting
On Tue, Jan 27, 2015, at 11:20 AM, Jon Baumgartner wrote:
> My app uses this call, and it worked fine until I sandboxed it. The
> documentation for this call says:
>
> > For sandboxed apps in OS X, the current home directory is not the same as
> > the user’s home directory. For a sandboxed app, t
> On Jan 27, 2015, at 1:34 PM, Quincey Morris
> wrote:
>
> On Jan 27, 2015, at 11:06 , Richard Charles wrote:
>>
>> That is a key-value coding method.
>
> It’s not, as Kyle just said.
Okay, you both win. It is a method which supports key-value coding.
Richard Charles
___
:) Thank you very much for your reply.
I need the recent documents list. So, I will not remove it.
I am still curious how the window list doesn’t appear on the dock menu of the
interested app.
Probably they removed Window menu from “menu bar”?
I checked if a window is excluded from window list wi
> On Jan 27, 2015, at 1:34 PM, Quincey Morris
> wrote:
>
> FWIW, there is yet another way to get to backing store from a custom
> primitive accessor — define another, private, Core Data property, and use
> *its* primitive accessors. This may seem clunky, but it’s officially
> countenanced in
> On 2015 Jan 27, at 13:25, JongAm Park wrote:
>
> I am still curious how the window list doesn’t appear on the dock menu of the
> interested app.
> Probably they removed Window menu from “menu bar”?
More likely, they just didn’t put it in there to begin with. The Dock Menu is
different than
I solved my problem and would like to share how I did it.
I’m working on a heavily customized app on top of Cocoa/Carbon.
So, general paradigm of Cocoa and Carbon is partially applied : how to enable
menu items, how to make windows, and so on.
However, there is a link to Cooca at the bottom of ou
> On 28 Jan 2015, at 01:50, Thomas Wetmore wrote:
>
>
>> On Jan 27, 2015, at 12:06 PM, Steve Mills wrote:
>>
>> On Jan 27, 2015, at 10:48:29, Roland King wrote:
>>>
Using IB to check the constraints on the NSTextField within the
NSTableCellView, IB states: “The selected vie
When I use AVPlayer to play a video file, I get a massive number of messages
logged from mpeg2parser, e.g:
> mpeg2parser VideoFrameCheckAdjustmentQueue: moving from adjustment queue -
> pts 74445210
> mpeg2parser VideoFrameCheckAdjustmentQueue: video 256 move from adjustment
> queue - good dts
On Tue, Jan 27, 2015, at 05:34 PM, Roland King wrote:
> No I don’t think so. I can’t think of a case IB adds constraints to
> anything automatically at this point.
If you do not specify any constraints on a view, at compile time Xcode 6
will install leading, top, width, and height constraints to m
On Tuesday, January 27, 2015, Graham Cox wrote:
> When I use AVPlayer to play a video file, I get a massive number of
> messages logged from mpeg2parser, e.g:
>
> > mpeg2parser VideoFrameCheckAdjustmentQueue: moving from adjustment queue
> - pts 74445210
> > mpeg2parser VideoFrameCheckAdjustmentQ
> On 28 Jan 2015, at 08:35, Kyle Sluder wrote:
>
> On Tue, Jan 27, 2015, at 05:34 PM, Roland King wrote:
>> No I don’t think so. I can’t think of a case IB adds constraints to
>> anything automatically at this point.
>
> If you do not specify any constraints on a view, at compile time Xcode 6
>
> On 2015 Jan 27, at 12:44, Keary Suska wrote:
>
> What exactly happened when you specified the setter, but not the getter?
I said I wasn’t sure because the project has a bunch of warnings due to ongoing
major rework, but I just retested again. Answer: Compiler does *not* warn if
you have a
> On Jan 27, 2015, at 7:48 PM, Roland King wrote:
>
>> On 28 Jan 2015, at 08:35, Kyle Sluder wrote:
>>
>> On Tue, Jan 27, 2015, at 05:34 PM, Roland King wrote:
>>> No I don’t think so. I can’t think of a case IB adds constraints to
>>> anything automatically at this point.
>>
>> If you do not
> On Jan 27, 2015, at 19:25, Thomas Wetmore wrote:
>
> I defer to the experts. But for me view-based tables no longer work 'as
> expected’ (how they worked with cell-based tables). That is, one now has to
> explicitly add constraints in order to get the text in cells to widen and
> shrink prop
On Jan 27, 2015, at 17:21 , Jerry Krinock wrote:
>
> Compiler does *not* warn if you have a custom primitive setter without a
> getter.
FWIW, the compiler doesn’t warn you if you have any setter without a getter.
> I also tried to get it to compile without declaring the instance variable
> th
On 27 Jan 2015, at 5:53 pm, Steve Mills wrote:
> I 100% agree. A table column that does not auto-resize is a very poor design.
> No right UX designer would make it do that.
The table column resizes just fine -- the issue is that you need to specify how
you want the stuff within to resize in ac
43 matches
Mail list logo
