Yeah, it was obvious that writeRowsWith: would soon be deprecated. After going
through the documentation a bit, I did it via:
func tableView(_ tableView: NSTableView, draggingSession session:
NSDraggingSession, willBeginAt screenPoint: NSPoint, forRowIndexes rowIndexes:
IndexSet) {
What is the alternative, then?
If single image drags will not work because of this, is there a means to
impersonate another method?
Oh, and greets from the coast of Africa. Cheers,
Alex Zavatone
Sent from my iPhone
> On Apr 20, 2019, at 10:17 AM, Rob Petrovec wrote:
>
> Because dragImage is
Because dragImage is the old (and likely soon to be deprecated), single image
style drag setup and the pasteboardWriter version is the modern multi-image
drag set up. Ever notice how when you drag a file around in the Finder the
drag image will morph as the drag moves between windows with diffe
Override:
- (NSArray *)draggingImageComponents;
Apple uses it in its sample TableViewPlaygroud. I found it using br -n
"-[NSDraggingImageComponent initWithKey:]". lldb and breakpoints can help
you. Use hopper or class-dump to see method names (AppKit).
Marek.
On Fri, Dec 15, 2017 at 6:52 PM,
You probably want NSTableView
-dragImageForRowsWithIndexes:tableColumns:event:offset:
—Rob
> On Dec 15, 2017, at 10:52 AM, David Catmull wrote:
>
> In my table view, when you drag an item, the drag image it uses comes from
> the column cell where the drag started, rather than using the cell f
The effect I don’t like about the default code is that when the last column’s
width is set to fill out the table, it’s only set for the current set of
widths. As soon as you narrow an earlier column, the last column’s right border
becomes visible. I want the last column to always max out, no mat
On Mar 15, 2017, at 06:51 , Stephane Sudre wrote:
>
> the Column Sizing option
Remember too that each column has its own sizing options that operate in
conjunction with the table view’s options. For each column, you can decide
whether the column participates in autoresizing (separately from wh
On Wed, Mar 15, 2017 at 9:59 AM, Daryle Walker wrote:
> 1. Is there a way to make the last (right in the U.S. localization) column to
> always be at the end of the table-view, instead of a gap after a resize?
Yes, there is.
> 2. My table has two columns. Is there a way to keep their sizes in pr
On Mar 15, 2017, at 03:59:43, Daryle Walker wrote:
>
> 1. Is there a way to make the last (right in the U.S. localization) column to
> always be at the end of the table-view, instead of a gap after a resize?
>
> 2. My table has two columns. Is there a way to keep their sizes in proportion
> af
On Jul 23, 2016, at 7:53 AM, Frank D. Engel, Jr. wrote:
>
> Does anyone know if there is a way to determine which column of an
> NSTableView something being dragged is dropped onto?
>
> I have drag and drop from one table in my application onto a row of another
> table working, but I would lik
> On Jul 23, 2016, at 6:53 AM, Frank D. Engel, Jr. wrote:
>
> Does anyone know if there is a way to determine which column of an
> NSTableView something being dragged is dropped onto?
>
> I have drag and drop from one table in my application onto a row of another
> table working, but I would
> On May 6, 2016, at 1:03 PM, Matthew LeRoy wrote:
>
> Hello,
>
> I'm having an issue where an NSTableView appears to be messaging its delegate
> after the delegate has been deallocated, causing an EXC_BAD_ACCESS crash. It
> doesn't always happen, but it happens regularly. My understanding is
On May 8, 2016, at 13:19, Quincey Morris
wrote:
If you look at your backtrace again, you’ll see that it crashed doing
something with rows. It’s as likely trying to message your data source as your
delegate. You should nil that as well. Note that it’s not necessarily that any
p
On Fri, 6 May 2016 13:28:10 -0700, Jens Alfke said:
>> On May 6, 2016, at 1:03 PM, Matthew LeRoy wrote:
>>
>> My understanding is that NSTableView's delegate is a zeroing weak reference
>
>Are you sure? Historically it’s been unsafe_unretained — in the old days
>before weak references or ARC, th
On 08 May 2016, at 21:19, Matthew LeRoy wrote:
> Unfortunately, setting the table view’s delegate to nil during tear-down
> (either in -windowWillClose: or in NSViewController’s -dealloc) doesn’t seem
> to fix the issue. I still get random but regularly reproducible crashes, with
> the same sta
On May 8, 2016, at 12:19 , Matthew LeRoy wrote:
>
> Unfortunately, setting the table view’s delegate to nil during tear-down
> (either in -windowWillClose: or in NSViewController’s -dealloc) doesn’t seem
> to fix the issue. I still get random but regularly reproducible crashes, with
> the same
> On May 8, 2016, at 12:19 PM, Matthew LeRoy wrote:
>
> Unfortunately, setting the table view’s delegate to nil during tear-down
> (either in -windowWillClose: or in NSViewController’s -dealloc) doesn’t seem
> to fix the issue. I still get random but regularly reproducible crashes, with
> the
>On May 6, 2016, at 1:03 PM, Matthew LeRoy wrote:
>
> My understanding is that NSTableView's delegate is a zeroing weak
> reference
>
>
>Are you sure? Historically it’s been unsafe_unretained — in the old days
>before weak references or ARC, the view never retained nor released the
>deleg
> On May 6, 2016, at 1:03 PM, Matthew LeRoy wrote:
>
> My understanding is that NSTableView's delegate is a zeroing weak reference
Are you sure? Historically it’s been unsafe_unretained — in the old days before
weak references or ARC, the view never retained nor released the delegate. The
typ
> On 6 May 2016, at 21:03, Matthew LeRoy wrote:
>
> Hello,
>
> I'm having an issue where an NSTableView appears to be messaging its delegate
> after the delegate has been deallocated, causing an EXC_BAD_ACCESS crash. It
> doesn't always happen, but it happens regularly. My understanding is th
> Ahh, the case of ambiguous ui
>
> Perhaps Disable OK while editing a cell; enable when edit ends, so
> Return Return accepts then closes?
>
> Gary
So how do I tell when editing begins since the control delegate is not
called when editing actually begins, but rather when the first key is
pr
On Jan 14, 2016, at 4:38 PM, Alex Kac wrote:
>
> I have a NIB with two views that I want to use depending on circumstances. I
> call one “weatherCell” and one “weatherCellNarrow”.
>
> I register it like this:
>
> - (NSString*)identifierForWeatherCell {
> return _narrowView ? @"weatherCe
On Jan 14, 2016, at 15:09 , Alex Kac wrote:
>
> Actually there is - the identifier. You set the NIB *and* the identifier.
Now that I’ve had time, I think I remember doing exactly this sometime in the
past. How soon we forget.
> And I was able to make it work right after I sent the email (isn
Actually there is - the identifier. You set the NIB *and* the identifier. And
I was able to make it work right after I sent the email (isn’t that how it is
always?) It seems that my “isNarrow” property wasn’t being set by the time the
view was loading where we were initializing it. I wasn’t abl
On Jan 14, 2016, at 14:38 , Alex Kac wrote:
>
> I can’t seem to get a good answer to if this should work or not (having
> multiple cellViews in one NIB).
No. There are 2 top level objects in your nib, but there’s nothing that tells
the table view machinery which one to use. (Normally, you’d u
> On 1 Oct 2015, at 5:04 pm, Peter Hudson wrote:
>
> Legacy code I’m afraid Graham - written some years ago.
> I simply want it to look better for now while we're getting on with the
> re-write.
> The new version indeed uses view-based table views - and works a lot better.
OK, so you’re impl
Legacy code I’m afraid Graham - written some years ago.
I simply want it to look better for now while we're getting on with the
re-write.
The new version indeed uses view-based table views - and works a lot better.
Peter
> On 1 Oct 2015, at 01:11, Graham Cox wrote:
>
>
>> On 30 Sep 2015,
> On 30 Sep 2015, at 10:20 pm, Peter Hudson wrote:
>
> As the user scrolls one of the table views, the system does not render all
> the details in the rows correctly.
> The most obvious one :- I draw my own lines between rows - inserting
> separator lines where appropriate.
> Hence, I overri
Sounds like you should be doing that in custom row views that draw the lines
when necessary
Sent from my iPhone
> On Sep 30, 2015, at 9:20 PM, Peter Hudson wrote:
>
> Many thanks for these ideas.
>
> As the user scrolls one of the table views, the system does not render all
> the details in
Many thanks for these ideas.
As the user scrolls one of the table views, the system does not render all the
details in the rows correctly.
The most obvious one :- I draw my own lines between rows - inserting
separator lines where appropriate.
Hence, I override drawRect. The process in here to
Check the NSScrollView notifications.
However you could try to observe changes to the NSClipView bounds.
You could also observe scroll events and so forth.
But ultimately you will run into semantics. Resting touches, momentum phases,
some slight ambiguity on whether the user feels done scrolling
Ken, Thanks for this insight.
Reading through your comments, I suspect the best way to deal with this is to
switch entire table views in and out ( or, perhaps, deal with datasources ).
I’ll probably do it with table view swapping as this avoids setting up the
views with each change.
Regard
On Sep 26, 2015, at 5:13 AM, Peter Hudson wrote:
> I have an NSTableView in my app which has started to behave differently on
> 10.10.
>
> I periodically change the datasource and delegate to the table view ( which
> is on screen )
> This has worked perfectly up until recently.
>
>
> After h
I went ahead and used a DTS ticket and the response I got back from Apple is
that there is no supported way to do what I want.
So, I am left with something custom or attempting to fake it by determining the
number of rows I need to fill the table (when there aren’t enough already) and
ordering
One way to do this is to not use a table view but just a simple scroll/clip
view setup and embed your content within it, pinning it only to the left,
right, and bottom edges of the clip view and do your drawing in that view. You
might be able to do it with a table view (and the typically associa
Again that is not the question he was asking. He wants to know how to have a
tableview which, if it has say one single row, shows that one single row at the
bottom of the enclosing scrollview instead of at the top.
Inserting the rows in order is not his problem, its’ getting the table view to
Data order is the simplest way to do what you want.
Just insert everything at the end.
Then also ensure no sorting.
Sent from my iPhone
> On Sep 1, 2015, at 7:27 PM, Eric Gorr wrote:
>
>
>> On Aug 31, 2015, at 10:00 PM, Keary Suska wrote:
>>
>> On Aug 31, 2015, at 7:51 PM, Eric Gorr wrot
You can move the table view to the bottom of the scroll view in an override of
-[NSScrollView tile].
Déjà vu
http://cocoa-dev.apple.narkive.com/cwH1sLmk/nstableview-with-reversed-rows
- Willeke
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
> On 1 Sep 2015, at 18:27, Eric Gorr wrote:
>
>>
>> On Aug 31, 2015, at 10:00 PM, Keary Suska wrote:
>>
>> On Aug 31, 2015, at 7:51 PM, Eric Gorr wrote:
>>>
>>> Normally when one adds the first row to a NSTableView, it will appear at
>>> the top of the view and additional rows will appear
> On Aug 31, 2015, at 10:00 PM, Keary Suska wrote:
>
> On Aug 31, 2015, at 7:51 PM, Eric Gorr wrote:
>>
>> Normally when one adds the first row to a NSTableView, it will appear at the
>> top of the view and additional rows will appear below it. Is it possible to
>> have the first row appear
On Aug 31, 2015, at 7:51 PM, Eric Gorr wrote:
>
> Normally when one adds the first row to a NSTableView, it will appear at the
> top of the view and additional rows will appear below it. Is it possible to
> have the first row appear at the bottom of the NSTableView and for new rows
> to appear
> On 26 Jul 2015, at 22:17, Ken Thomases wrote:
>
> The right approach is to subclass NSTableRowView. It's not hard. Why do you
> resist it?
>
OK, got it. Thanks for the pointers. Much appreciated!
Best
Phil
___
Cocoa-dev mailing list (Cocoa-
On Jul 26, 2015, at 7:25 AM, 2551 <2551p...@gmail.com> wrote:
> I’ve been struggling with NSTableView for the last two days. All I want to do
> is ensure the alternative “gray” highlight is used on a selection
> consistently instead of the heavy blue.
My first question is why do you want to tri
> On 1 Jul 2015, at 09:37, Ken Thomases wrote:
>
> On Jun 30, 2015, at 11:56 AM, Jonathan Guy wrote:
>
>> Im trying to fix a problem with dynamic row heights with auto layout and
>> bindings which was working fine in an older build of Xcode but which now no
>> longer works. So my new attempt
On Jun 30, 2015, at 11:56 AM, Jonathan Guy wrote:
> Im trying to fix a problem with dynamic row heights with auto layout and
> bindings which was working fine in an older build of Xcode but which now no
> longer works. So my new attempt for the most part works but about 30% of my
> row heights
On Apr 15, 2015, at 12:41 AM, Alex Kac wrote:
> I’m failing to find the proper way to do this. Given an NSTableView, I’d
> like to size its parent view to the height of all the rows/content/headers
> of that table view so that there is no scrolling.
>
> Someone suggested:
>
> [_scrollView.docum
Lee Ann,
thank you for pointing me to the TextEdit sources which I had already
checked. They do not even contain the terms "NSTable" or "NSTextTable"
at all. TextEdit seems to keep all text content in a simple NSTextView.
They just added the system method -orderFrontTablePanel: to the app menu
You can get TextEdit's source code and see how they did it:
https://developer.apple.com/library/mac/samplecode/textedit/Introduction/Intro.html
From: cocoa-dev-bounces+lrucker=vmware@lists.apple.com
[cocoa-dev-bounces+lrucker=vmware@lists.apple.com
Well, that page gives you enough example code to make it trivial to create one,
try it out, and see if it does what you need. :-)
--
Charles
On Thursday, October 16, 2014 at 10:43, Ulf Dunkel wrote:
> Charles,
>
> so I should investigate on NSTextTable instead of NSTableView, right?
>
>
Charles,
so I should investigate on NSTextTable instead of NSTableView, right?
- - - - -
Am 16.10.2014 um 14:41 schrieb Charles Jenkins:
Ulf,
As you can see from my text view struggles, I’m no expert, but I don’t
think you’ll have a lot of success trying to stick an NSTableView into
an NSText
Ulf,
As you can see from my text view struggles, I’m no expert, but I don’t think
you’ll have a lot of success trying to stick an NSTableView into an NSTextView.
The kind of table you put inside a text view is a different animal: really just
a fancy attributed string the text system knows how
Op 2 okt 2014, om 23:13 heeft Luc Van Bogaert het volgende geschreven:
> That's not exactly what I meant, but it might be part of a solution.
>
> I want the table to populate 'from the bottom to the top', so that the free
> space in the scrollview (if there is any) is at the top, above the top
On 3 Oct 2014, at 07:25, Luc Van Bogaert wrote:
> Sure, the table will display 'layer' objects that can be stacked onto each
> other. So the first layer should be displaced at the bottom of the stack, the
> second layer on top of the first, and so on... So in fact, I would like to
> have a t
On 3 Oct 2014, at 4:25 pm, Luc Van Bogaert wrote:
> Sure, the table will display 'layer' objects that can be stacked onto each
> other. So the first layer should be displaced at the bottom of the stack, the
> second layer on top of the first, and so on... So in fact, I would like to
> have a
Sure, the table will display 'layer' objects that can be stacked onto each
other. So the first layer should be displaced at the bottom of the stack, the
second layer on top of the first, and so on... So in fact, I would like to have
a table that represents a stack of objects that 'grows' upwards
On 3 Oct 2014, at 7:13 am, Luc Van Bogaert wrote:
> I want the table to populate 'from the bottom to the top', so that the free
> space in the scrollview (if there is any) is at the top, above the top row,
> instead of below the bottom table row.
May I ask why? Users are likely to be confuse
Why not enforce a minimum row count that accounts for the height of the table.
Then, have your data source provide dummy rows for the ones at the top, when
the actual count is less than the enforced count. You can have a special table
cell for the dummy rows, or just hide all the content that wo
That's not exactly what I meant, but it might be part of a solution.
I want the table to populate 'from the bottom to the top', so that the free
space in the scrollview (if there is any) is at the top, above the top row,
instead of below the bottom table row.
I hope I have expressed more clear
Have you considered just inverting the data source?
Thanks,
Jon
On Oct 2, 2014, at 12:45 PM, Luc Van Bogaert wrote:
> Hi,
>
> I would like to implement a table (in a scrollview) where the first row
> displays at the bottom instead of at the top, the second row above the first
> and so on. H
On 2 Oct 2014, at 20:45, Luc Van Bogaert wrote:
> Hi,
>
> I would like to implement a table (in a scrollview) where the first row
> displays at the bottom instead of at the top, the second row above the first
> and so on. How would I go about to accomplish this?
> I've tried overriding 'isFli
File a bug report. That's what betas are for.
> On 10 Jul, 2014, at 11:26, Appa Rao Mulpuri wrote:
>
> Right, why the functional breaks in the existing functionality?
>
> Sent from my iPhone
>
>>> On 09-Jul-2014, at 8:36 pm, Kyle Sluder wrote:
>>>
>>> On Jul 8, 2014, at 11:14 PM, Appa Rao
Right, why the functional breaks in the existing functionality?
Sent from my iPhone
> On 09-Jul-2014, at 8:36 pm, Kyle Sluder wrote:
>
>> On Jul 8, 2014, at 11:14 PM, Appa Rao Mulpuri
>> wrote:
>>
>> In Yosemite, TableView with the Sourcelist as selectionHighlightStyle with
>> the cell based
On Jul 8, 2014, at 11:14 PM, Appa Rao Mulpuri wrote:
>
> In Yosemite, TableView with the Sourcelist as selectionHighlightStyle with
> the cell based drawing
Cell-based table views are deprecated.
--Kyle Sluder
___
Cocoa-dev mailing list (Cocoa-dev@l
Thanks Ken, I was missing constrains that was causing the issue. I see the
document states that Xcode will not complain if there are not enough
constrains. It would have helped of it did. I didn¹t realise the problem
was constrains. Do you know why this behaviour and if possible someway to
enable X
On Jul 1, 2014, at 6:46 PM, Varun Chandramohan wrote:
> I have a NSTableView (View based) with 8 NSTableColumn each of which has
> NSTableCellView as default built from IB. I followed apple guide
> https://developer.apple.com/library/mac/documentation/Cocoa/Conceptual/TableView/Introduction/Intr
On 26 Jun 2014, at 13:16, Jonathan Mitchell wrote:
>
> On 25 Jun 2014, at 16:41, Ken Thomases wrote:
>>
>> Couldn't you return a custom row view using -tableView:rowViewForRow: and
>> then return no cell views for that row by returning nil from
>> -tableView:viewForTableColumn:row:?
>>
> C
On 25 Jun 2014, at 16:41, Ken Thomases wrote:
>
> Couldn't you return a custom row view using -tableView:rowViewForRow: and
> then return no cell views for that row by returning nil from
> -tableView:viewForTableColumn:row:?
>
Customising the group row behaviour does seem like the answer here
> On Jun 25, 2014, at 10:41 AM, Ken Thomases wrote:
>
> Couldn't you return a custom row view using -tableView:rowViewForRow: and
> then return no cell views for that row by returning nil from
> -tableView:viewForTableColumn:row:?
IIRC, this doesn’t present correctly to VoiceOver.
--Kyle
___
On Jun 25, 2014, at 9:48 AM, Kyle Sluder wrote:
> On Jun 25, 2014, at 9:07 AM, Jonathan Mitchell
> wrote:
>>
>> The docs for
>>
>> - (NSCell *)tableView:(NSTableView *)tableView
>> dataCellForTableColumn:(NSTableColumn *)tableColumn row:(NSInteger)row
>> say
>>
>> A different data cell can
On Jun 25, 2014, at 9:07 AM, Jonathan Mitchell wrote:
>
> The docs for
>
> - (NSCell *)tableView:(NSTableView *)tableView
> dataCellForTableColumn:(NSTableColumn *)tableColumn row:(NSInteger)row
> say
>
> A different data cell can be returned for any particular table column and
> row, or a c
On Feb 10, 2014, at 9:01 PM, Trygve Inda wrote:
>
> I have several NSTableViews in my windows. One of them only highlights a new
> row on mouseUp, while the others highlight the clicked row on mouseDown.
>
> How can I fix the one table so that it too highlights on mouseDown?
Yeesh, and here I a
Hitting return results in the Table losing focus, the selected row
highlight
turns grey and controlTextDidEndEditing is never called.
Upon further research, it only does this when the column being edited is
included in the sort descriptors for the table view.
__
> I have an NSTableView backed by an NSArrayController.
I call
> setFilterPredicate on the NSArrayController to set a predicate of
"rating ==
> 2" This does filter the table to show only those entries where
rating is
> 2.
The rating column is a Level Indicator and set to show star ratings in
> IB
On Nov 20, 2013, at 10:00 AM, Todd Heberlein wrote:
> Embarrassingly simple problem, but I can’t figure it out.
>
> ...
> - (void)awakeFromNib
> {
> [self.jocksTable registerForDraggedTypes: [NSArray arrayWithObjects:
> NSPasteboardTypeString, nil]];
> [self.jocksTable setDraggingS
On Nov 20, 2013, at 10:00 AM, Todd Heberlein wrote:
> I’m trying a very simple test (I just want the string “foo” to be dropped in
> an email message) that I cannot seem to make work. What am I missing?
> (setString:forType: is returning YES)
>
>
> - (BOOL)tableView:(NSTableView *)tv
> writeR
In the end I’ve resorted to listening for frame changes in my tableview
subclass then I get the list of visible rows and force a redraw (via
setNeedsDisplay) on the row views. I also have to propagate this to the child
views which are the NSTextFields which were appearing black. Now I get an ugl
Implementing this doesn’t seem to make any difference. I checked that it is
called. In any case, the release notes say that responsive scrolling is not
active if you link against 10.7, which I do.
Martin
On 25 Oct 2013, at 08:47 pm, Michael Cinkosky
wrote:
> I believe you need to implement a
I believe you need to implement a new delegate method for this table:
+(BOOL) isCompatibleWithResponsiveScrolling {
return NO;
}
https://developer.apple.com/library/prerelease/mac/releasenotes/AppKit/RN-AppKit/index.html#//apple_ref/doc/uid/TP3741-CH2-SW28
Michael
On Oct 25, 2013
On Jun 22, 2013, at 17:52 , Nick Zitzmann wrote:
> I did search the documentation and the archives, and didn't see anyone
> talking about this. It appears that, in view-based NSTableViews or
> NSOutlineViews, if a row is designated as a group row/item, then the view
> spans the entire column,
On Feb 12, 2013, at 11:26 PM, Alex Rainchik wrote:
> Hello,
>
> I have a typical NSTableView and NSArrayController confguration, with Array
> Controller's Content Array bound to NSMutableArray called "usersArray"
>
> What I'm trying to do is to have an KVO observer setup, so every time
> usersA
On Jan 26, 2013, at 4:08 AM, Ivan Ostres wrote:
> I am trying to use performClickOnCellAtColumn on NSTableView to put cell in
> editing mode (like when you create a new folder in Finder). If I click on the
> cell I can change it content but using performClickOnCellAtColumn nothing
> happens. T
On Jan 24, 2013, at 6:46 PM, Chuck Soper wrote:
> On 1/24/13 6:30 PM, "Quincey Morris"
> wrote:
>
>> It's clearly documented that they're optional in your situation, and the
>> documentation is 10.7-vintage. The 10.8 SDK header file also says they're
>> optional. They may not be optional pre-1
On 1/24/13 6:30 PM, "Quincey Morris"
wrote:
>On Jan 24, 2013, at 18:11 , Chuck Soper wrote:
>
>> If I do not implement numberOfRowsInTableView: and
>> tableView:objectValueForTableColumn:row: then this error is written to
>>the
>> console:
>>
>> *** Illegal NSTableView data source (< MyCustomVi
On Jan 24, 2013, at 18:11 , Chuck Soper wrote:
> If I do not implement numberOfRowsInTableView: and
> tableView:objectValueForTableColumn:row: then this error is written to the
> console:
>
> *** Illegal NSTableView data source (< MyCustomView: 0x1019ab7b0>). Must
> implement numberOfRowsInTabl
On 1/24/13 5:48 PM, "Quincey Morris"
wrote:
>On Jan 24, 2013, at 17:37 , Graham Cox wrote:
>
>> If the table view has a dataSource assigned, it has to be "legal",
>>which means it must implement those two methods. The fact that, with
>>bindings, they may not ever be called is irrelevant. The dat
On Jan 24, 2013, at 17:48 , Quincey Morris
wrote:
> NSTableViewDelegate
Ugh, I meant NSTableViewDataSource. I'm at a 100% hit rate for non-misspelled
typos in the last couple of days. Ditto "well-reasonable".
___
Cocoa-dev mailing list (Cocoa-dev@l
On Jan 24, 2013, at 17:37 , Graham Cox wrote:
> If the table view has a dataSource assigned, it has to be "legal", which
> means it must implement those two methods. The fact that, with bindings, they
> may not ever be called is irrelevant. The dataSource must conform to the
> compulsory proto
On 25/01/2013, at 12:31 PM, Chuck Soper wrote:
> When I use bindings for NSTableView and implement drag and drop, an
> "Illegal NSTableView data source" error is written to the console. This is
> because I use NSTableViewDataSource methods to implement drag and drop.
>
> I'm able to prevent the
OK, well I accidentally solved this part satisfactorily.
In my -animationForKey: method, I set the animationDuration to several seconds
to check it was really having an effect, and to my surprise I found that this
also affected the animation in the table view. I think this happens because the
b
On 21/11/2012, at 7:21 PM, Graham Cox wrote:
> Hi all,
>
> I'm using [NSTableView moveRowAtIndex:toIndex:] to show an animation for a
> row reordering on drag/drop.
I also have a related question:
Is it possible to show a table row animation during the drag to have a gap open
where the dro
Am 02.10.2012 um 11:56 schrieb Евсеев Алексей:
> sorry for my english
>
> I have a form with NSTableView and two button "add" and "remove"
>
> "Add" button add's item into datasource array. And new row will show only
> after restart program.
>
> "Remove" button remove item from array. While
It is a view setting you can turn off in the IB.
Sent from my Verizon Wireless BlackBerry
-Original Message-
From: Alfian Busyro
Sender: cocoa-dev-bounces+zav=mac.com@lists.apple.comDate: Wed, 26 Sep 2012
13:55:10
To: Corbin Dunn
Cc:
Subject: Re: nstableview without nsscrollview
setVerticalScrollElasticity:
As it happens I just noticed this existence of this property today.
--Andy
On Sep 26, 2012, at 1:32 AM, Gary L. Wade wrote:
> There's an elastic setting, which I don't recall the exact name or settings,
> but you just turn those off to get rid of the bounce.
> --
There's an elastic setting, which I don't recall the exact name or settings,
but you just turn those off to get rid of the bounce.
--
Gary L. Wade (Sent from my iPhone)
http://www.garywade.com/
On Sep 25, 2012, at 9:55 PM, Alfian Busyro wrote:
> Thanks for the answer.
>> Just leave it in a scro
Thanks for the answer.
Just leave it in a scrollview, and set it to not scroll in any direction, and
size the scrollview to the table's height/width. That's it.
Actually I did it, In IB I deselect "Show Horizontal Scroll" and "Show
Vertical Scroll" the table view won't scroll but still bouncin
On Sep 10, 2012, at 6:08 PM, Alfian Busyro wrote:
> Kyle, thanks for your solution.
>> Think very hard about this. Why would you want to do this? What would
>> you do if your table view gained enough data that it no longer fit in
>> the available space?
> So I planning to make two tables in one
Kyle, thanks for your solution.
Think very hard about this. Why would you want to do this? What would
you do if your table view gained enough data that it no longer fit in
the available space?
So I planning to make two tables in one view but I don't want to
separate that two tables with scroll,
On Sun, Sep 9, 2012, at 11:17 PM, Alfian Busyro wrote:
> I'm thinking to have an un-scrollable nstableview in mac-osx app.
> because I don't want user to scroll within the table, but have to
Think very hard about this. Why would you want to do this? What would
you do if your table view gained enou
On Wed, Aug 8, 2012, at 04:37 PM, Kyle Sluder wrote:
> It does make it easier for subviews that want to perform their own
> NSEvent handling to do so, but now I'm having the darndest time figuring
> out how that interacts with the highlight NSTableView draws around
> right-clicked rows. It's suppos
On 09/08/2012, at 5:31 PM, Quincey Morris
wrote:
>> So call super, but you need to know whether it's going to call through your
>> -init method or not (for cells, it does not).
>
> Except that you do sort-of know (I think). If it does, all your instance
> variables are 0. If you have object-
1 - 100 of 676 matches
Mail list logo
