On 15 Aug 2014, at 04:55, Graham Cox wrote:
> I ask because I'm having trouble getting part of my interface working with
> autolayout, though other parts work fine. Since the part that doesn't work
> works just fine with struts-and-springs, and has done for a long time, I'm
> wondering if I c
On 14 Aug 2014, at 19:24, Roland King wrote:
>>
>> class AppDelegate: NSObject
>> {
>> dynamic var statusString : String? // bound to some TextField
>>
>> let someThing = SomeClass( myStatusHandler )< this
>> creates strange error messages
>>
>> func
After being impressed with bindings for an NSTableView, I’m looking at what I
can do for a standalone NSPopupButton, in the hope of reducing the amount of
glue code I have. The button isn’t just a simple one though, I need to:
- Include separator items
- Disable (grey out) some items
- Select mul
On Aug 15, 2014, at 5:23 AM, Jonathan Taylor
wrote:
> After being impressed with bindings for an NSTableView, I’m looking at what I
> can do for a standalone NSPopupButton, in the hope of reducing the amount of
> glue code I have. The button isn’t just a simple one though, I need to:
> - Inclu
>> After being impressed with bindings for an NSTableView, I’m looking at what
>> I can do for a standalone NSPopupButton, in the hope of reducing the amount
>> of glue code I have. The button isn’t just a simple one though, I need to:
>> - Include separator items
>> - Disable (grey out) some ite
I use a “[[NSUUID UUID] UUIDString]” to make every instance’s name unique. But
the reference docs plus some sample code just use the XIB’s name. Am I
overthinking it? What is this name for? Can we get away with multiple WebView
instances within the same app having the same ID?
—
Daryle Wal
On Fri, Aug 15, 2014, at 10:42 AM, Daryle Walker wrote:
> I use a “[[NSUUID UUID] UUIDString]” to make every instance’s name
> unique. But the reference docs plus some sample code just use the XIB’s
> name. Am I overthinking it? What is this name for? Can we get away
> with multiple WebView ins
> On Aug 15, 2014, at 9:49 AM, Kyle Sluder wrote:
>
> You should probably be using the new API.
…unless you want to support customers who haven't upgraded to 10.10. Which I
imagine is true of a lot of developers.
(Me, I can't consider using iOS 8 or OS X 10.10 features for at least another
y
I've just created a new OS X project from Xcode 5.1.1. Simple project, one
window, one tableview set to use NSTableCellView. I have a few UI items in
the table cell view. Nothing fancy, a couple of NSTextFields and an
NSProgressIndicator.
Now, I implement *tableView:viewForTableColumn:row:*. Based
On Aug 15, 2014, at 14:09 , Laurent Daudelin wrote:
> Now, I implement *tableView:viewForTableColumn:row:*. Based on an array of
> dictionaries, I set the various UI items in the tableCellView that I get
> calling *makeViewWithIdentifier:owner:* passing the tableColumn identifier
> that is set to
On Aug 15, 2014, at 8:58 AM, Jonathan Taylor
wrote:
>>> After being impressed with bindings for an NSTableView, I’m looking at what
>>> I can do for a standalone NSPopupButton, in the hope of reducing the amount
>>> of glue code I have. The button isn’t just a simple one though, I need to:
>>
As I’m stripping out the NSDocument stuff, I realize that I need some sort of
global object to hold each window(-controller) as I create them, otherwise ARC
will purge them soon after creation. The application delegate seems like a
good option, as it’s my only other custom class and Apple uses
I subclass NSWindowController.
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subs
(reposted for formatting)
On Aug 15, 2014, at 16:24 , Daryle Walker wrote:
> As I’m stripping out the NSDocument stuff, I realize that I need some sort of
> global object to hold each window(-controller) as I create them, otherwise
> ARC will purge them soon after creation. The application de
On 15 Aug 2014, at 7:39 pm, Jonathan Mitchell wrote:
>
> On 15 Aug 2014, at 04:55, Graham Cox wrote:
>
>> I ask because I'm having trouble getting part of my interface working with
>> autolayout, though other parts work fine. Since the part that doesn't work
>> works just fine with struts-a
On 15 Aug 2014, at 8:17 pm, Graham Cox wrote:
> What I really want is that part of my view hierarchy to be free to use
> -setFrame:, but other parts use the autolayout constraints normally.
Can't you simply set translatesAutoresizingMaskIntoConstraints = NO on the
views in question? Then you
On Aug 15, 2014, at 8:44 PM, Ben Kennedy wrote:
>
>> On 15 Aug 2014, at 8:17 pm, Graham Cox wrote:
>>
>> What I really want is that part of my view hierarchy to be free to use
>> -setFrame:, but other parts use the autolayout constraints normally.
>
> Can't you simply set translatesAutoresizi
17 matches
Mail list logo
