ToDesignableDocument,
it should include a call to [super
ibDidAddToDesignableDocument:document].
Good luck -
Jon Hess
On Aug 8, 2008, at 12:17 AM, Cyril Kardassevitch wrote:
Thanks a lot Jon !
This perfectly solves the issue ! So, to verify that I do it
correctly...
I've overloaded the ibAddToDesignableDocument
't been added to the same document, then you'll
run into this sort of issue. Just make sure to invoke -[IBDocument
addObject:myFormatter toParent:myTextField] before calling
[myTextField setFormatter:myForamtter].
Hope that clears up your issue -
Jon Hess
On Aug 7, 2008, at 2:02 AM, Cyril
rangely this formatter is fully functional...
Cyril
Le 7 août 08 à 21:46, Michael Ash a écrit :
On Thu, Aug 7, 2008 at 2:54 PM, Cyril Kardassevitch
<[EMAIL PROTECTED]> wrote:
hi list,
I've investigated further and try to reproduce the problem with a
simpler
configuration. So
ick on the formatter
button (bottom right of the text field)
Obviously, I have missed something... Any idea ?
Thanks,
Cyril.
Le 7 août 08 à 11:02, Cyril Kardassevitch a écrit :
hi,
I have designed customs NSTextField and NSFormatter objects that I
have tried to pack in an interface builde
hi,
I have designed customs NSTextField and NSFormatter objects that I
have tried to pack in an interface builder 3 plugin...
This works fine (can drag and drop the field, can access field
inspector), except that when I select the formatter, interface builder
generates an assertion failur
