No, only Core Animation with simple CALayers.
Can it be indicative of some problems in my code, or should I just ignore it?
Everything seems to work fine otherwise. The messages are quite annoying
though. Besides, it seems that in previous version of my app the messages did
not appear, or
I have a table which has a list of items on which multiple actions can be
performed. Initially, I thought to use check box cells (there are only two
possible actions that can be performed on each item right now - so the list of
columns is manageable) I thought a little further about the
On Mar 24, 2013, at 1:17 PM, Oleg Krupnov oleg.krup...@gmail.com wrote:
No, only Core Animation with simple CALayers.
Can it be indicative of some problems in my code, or should I just ignore it?
Everything seems to work fine otherwise. The messages are quite annoying
though. Besides, it
All right, then what is Invalid Framebuffer? What kind of (mis)use of Core
Animation *might* produce this error? Too large layers? Zero sized layers? Some
combination of layer properties?
I've made some experiments trying to isolate the problem, and it seems that it
happens to layers whose
On Mar 24, 2013, at 2:14 PM, Oleg Krupnov oleg.krup...@gmail.com wrote:
All right, then what is Invalid Framebuffer? What kind of (mis)use of Core
Animation *might* produce this error? Too large layers? Zero sized layers?
Some combination of layer properties?
Invalid framebuffer basically
On Mar 24, 2013, at 13:47 , Pascal Harris 45rpmli...@googlemail.com wrote:
Question 1. Is this possible, and am I even using the correct tool to do the
job?
It's certainly possible to use popup buttons in a table column.
It's questionable whether this is the right tool for this job. Popup
With regard to the title to display, I was thinking of 'Activated' if actions
are selected (and by clicking on the pop up one can see exactly what actions
are selected), and 'Deactivated' if no selections have been made. That wording
might need a little work, but that's the gist of it.
As to
On Mar 24, 2013, at 14:50 , Pax 45rpmli...@googlemail.com wrote:
You may be more successful if you use a view-based table rather than a
cell-based table. One of the reasons we have view-based tables is to be able to
avoid dealing with cells directly, in situations like this.
However, if you've
Ah. I shall have to look that up. Do you know of any good examples for view
based tables?
As to the backtrace:
* thread #1: tid = 0x2403, 0x0001004cb55e DefaultPlugin`-[DefaultPlug
cellPreferenceChanged:](self=0x00010182a5b0, _cmd=0x000101826ea0,
sender=0x00010182cc00) + 30
It's important that we all check existing documentation before pestering this
list with a question.
I used to use the search capability in the Cocoa-dev list page
(https://lists.apple.com/mailman/listinfo/cocoa-dev), but that
disappeared at least a year ago, leaving only archive access to
On Mar 24, 2013, at 15:16 , Pax 45rpmli...@googlemail.com wrote:
Ah. I shall have to look that up. Do you know of any good examples for view
based tables?
Not really. You can work through the Apple documentation:
On Mar 24, 2013, at 15:25 , John Bartleson jfbartle...@me.com wrote:
How do you list denizens typically check to see if a problem has already been
solved before querying the list?
You can search via a mainstream search engine such as Google or DuckDuckGo by
including 'site:lists.apple.com'
On 25/03/2013, at 8:14 AM, Oleg Krupnov oleg.krup...@gmail.com wrote:
All right, then what is Invalid Framebuffer? What kind of (mis)use of Core
Animation *might* produce this error? Too large layers?
I think I've seen this error when using CAShapeLayer and the frame size
exceeded a
13 matches
Mail list logo
