I have an NSOutlineView built in IB, each column I added is automatically given
this same format (where indents imply children).
NSTableColumn
NSTableCellView
NSTextField
NSTextFieldCell
NSTextFieldCell (called ‘Text Cell’)
I believe I understand
That's correct.
You will have a cell (NSCell in the project I used to check) in the
hierarchy when you use a view-based table view.
I would tend to believe it's an IB bug that the data cell for the
TableColumn is displayed.
___
Cocoa-dev mailing list
I set my deployment target to be 10.5.
I see no warnings about using APIs not supported in 10.5.
My program crashes on 10.5.8 ... I do not haveth report from the customer as
yet.
Is there an efficient way to isolate APIs not supported ?
-rags
Hi Jerry and all,
You should look for … overrides of superclass properties
Yes, indeed. Search for the AppKit Release Notes for OS X 10.10 Yosemite and
carefully read the section on tab views, wherein Apple has added alot of new
stuff, which may be stepping on your old stuff.
Thanks!
On Dec 1, 2014, at 10:33 , Raglan T. Tiger r...@crusaderrabbit.net wrote:
I see no warnings about using APIs not supported in 10.5.
My program crashes on 10.5.8 ... I do not haveth report from the customer as
yet.
Is there an efficient way to isolate APIs not supported ?
There’s no
On Dec 1, 2014, at 10:41 , Andreas Höschler ahoe...@smartsoft.de wrote:
What the heck does that mean? How can they remove these access methods?
They didn’t. What they did is to change the access method declarations to
@property declarations. The change shows up in the API changes as a
I am looking for a way to work around the conflict between -[CALayer
cornerRadius] and +[NSBezierPath bezierPathWithRoundedRect:xRadius:yRadius].
These days, NSBezierPath apparently uses a new algorithm to draw rounded
corners on a rectangle, resulting in a smoother-appearing curve. However,
On Dec 1, 2014, at 12:16 PM, Milen Dzhumerov s...@milen.me wrote:
you don’t actually need to run the old Xcode, you only need the SDK itself
Ok, this seems like the easiest approach. Thanks.
-rags
___
Cocoa-dev mailing list
On Dec 1, 2014, at 10:41 AM, Andreas Höschler ahoe...@smartsoft.de wrote:
Hi Jerry and all,
You should look for … overrides of superclass properties
Yes, indeed. Search for the AppKit Release Notes for OS X 10.10 Yosemite
and carefully read the section on tab views, wherein Apple has
Hi Kyle,
Adding
#ifdef __APPLE__
- (void)setWindow:(NSWindow *)window
{
}
#endif
to my GSScrollView : NSScrollView subclass fixed (or at least worked around)
the issue (no exception anymore and no apparent malfunction of the app).
WOA. This is NOT the way to solve this
On Dec 1, 2014, at 1:08 PM, Andreas Höschler ahoe...@smartsoft.de wrote:
Hi Kyle,
Adding
#ifdef __APPLE__
- (void)setWindow:(NSWindow *)window
{
}
#endif
to my GSScrollView : NSScrollView subclass fixed (or at least worked
around) the issue (no exception anymore and no apparent
On 2 Dec 2014, at 6:19 am, Bill Cheeseman wjcheese...@gmail.com wrote:
Can anyone suggest another approach?
Not another approach, but a possible alternative explanation. Antialiasing.
Those curved corners will cause various nearby pixels to be rendered for
antialiasing, and these may
Layer-backed multline text fields are drawing dimmer than otherwise *identical*
layer-backed single line fields. The only difference is the multiline field
has a new line in its text value.
Here's an example:
http://sethwillits.com/temp/upshot/upshot_uR7h5QTy.png
This visible difference only
On Dec 01, 15:38 PM, sli...@araelium.com wrote:
Layer-backed multline text fields are drawing dimmer than otherwise
*identical*
layer-backed single line fields. The only difference is the multiline
field
has a new line in its text value. Here's an example:
14 matches
Mail list logo
