> On 5 Jul 2017, at 7:25 pm, Georg Seifert wrote:
>
> Any reason you set the tableview to be "Source List". Set it to regular and
> it will work perfectly. It seems that the NSPopUpButtonCell don’t like to be
> in a source list. Maybe you can subclass it and draw yourself?
Interesting… I don
Any reason you set the tableview to be "Source List". Set it to regular and it
will work perfectly. It seems that the NSPopUpButtonCell don’t like to be in a
source list. Maybe you can subclass it and draw yourself?
Georg
> On 05.07.2017, at 03:36, Graham Cox wrote:
>
>
>> On 5 Jul 2017, at
On Jul 4, 2017, at 18:23 , Graham Cox wrote:
>
> However, as of the latest documentation I can find, cell-based tables are not
> exactly deprecated. They’re just treated as the embarrassing brother no-one
> talks about, which is not quite the same thing:
I was basing it on this pages like this
> On 5 Jul 2017, at 11:23 am, Graham Cox wrote:
>
> If anyone can offer a place to host the project, I’d be happy to share it,
> and see whether the problem is seen by others. (I no longer have file hosting
> services).
Never mind - I remembered I had an Amazon S3 account.
http://s3.amazona
> On 5 Jul 2017, at 5:21 am, Quincey Morris
> wrote:
>
> OTOH, before you go to too much more trouble with this, it seems to me that
> your next step is to convert to a view-based table view. It’s really not that
> much work, and cell-based table views were deprecated in 10.10, which is
> ba
> On Jul 4, 2017, at 12:00 AM, Graham Cox wrote:
>
> Heh, well, I wish I knew.
> Instruments isn’t working. It’s a new machine which I set up from my older
> machine. XCode works fine, but Instruments doesn’t. I guess that just copying
> stuff over isn’t enough to install it.
FYI, you don’t n
On Jul 4, 2017, at 05:02 , Graham Cox wrote:
>
> But it’s still spending an excruciating amount of time rendering the title of
> the pop-up button, but most of it is in the mysterious rgba64_DAplusdDA
> function. This is called twice for each pop-up button rendered, and the time
> divides fair
> On 4 Jul 2017, at 6:02 pm, Graham Cox wrote:
>
> I can live with layer-backing as a solution, it doesn’t appear to have any
> downsides.
I spoke too soon.
Layer backing disguises the performance issue by capturing the first render
pass which is then used for scrolling. So scrolling is fas
On Jul 4, 2017, at 01:02 , Graham Cox wrote:
>
> Is NSTableView documented anywhere to require layer backing?
Not that I know of. A couple of things to keep in mind:
— This thing about the dramatic effect *might* be specific to NSCell-based
table views (i.e. in a sense they no longer care abo
> On 4 Jul 2017, at 5:39 pm, Quincey Morris
> wrote:
>
> On Jul 4, 2017, at 00:18 , Graham Cox wrote:
>>
>> Is there a way to opt-out of vibrancy for an entire table view?
>
> There’s no clear indication that the performance problem has anything to do
> with vibrancy.
True, but the -[NSCel
On Jul 4, 2017, at 00:18 , Graham Cox wrote:
>
> Is there a way to opt-out of vibrancy for an entire table view?
There’s no clear indication that the performance problem has anything to do
with vibrancy. In both cases, the “expensive” call was about transparency,
which could just be about comp
> On 4 Jul 2017, at 5:00 pm, Graham Cox wrote:
>
>
>> On 4 Jul 2017, at 12:29 pm, Quincey Morris
>> wrote:
>>
>> On Jul 3, 2017, at 18:19 , Graham Cox wrote:
>>>
>>> slow. as. molasses.
>>
>> What does Instruments say it’s doing?
>>
>
>
> Heh, well, I wish I knew.
>
> Instruments isn’
> On 4 Jul 2017, at 12:29 pm, Quincey Morris
> wrote:
>
> On Jul 3, 2017, at 18:19 , Graham Cox wrote:
>>
>> slow. as. molasses.
>
> What does Instruments say it’s doing?
>
Heh, well, I wish I knew.
Instruments isn’t working. It’s a new machine which I set up from my older
machine. XCod
isn't this what Instruments is supposed to be good at telling you?
On 04/07/2017 11:07, Alex Zavatone wrote:
Stab in the dark, but what is your cell identifier value?
I have seen WAY TOO MUCH CODE where people have created a different cell
identifier for each cell.
Also, on iOS, there is a m
Stab in the dark, but what is your cell identifier value?
I have seen WAY TOO MUCH CODE where people have created a different cell
identifier for each cell.
Also, on iOS, there is a method called prepareCellForReuse that might apply
here.
You can also log when the cell is displayed at the star
On Jul 3, 2017, at 18:19 , Graham Cox wrote:
>
> slow. as. molasses.
What does Instruments say it’s doing?
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the modera
I have a NSTableView, cell-based (partially because it’s a very long-standing
piece of code, partially because it is just a table of values which a
cell-based table is ideally suited to - view-based would not do anything for me
here).
This table has always worked fine, but in Sierra, it is slow
17 matches
Mail list logo
