On Apr 7, 2014, at 9:13 PM, Quincey Morris
wrote:
> On Apr 7, 2014, at 20:43 , Michael de Haan wrote:
>
>> I have implemented a custom UITableViewCell in a (test) project with batch
>> deletions, following the guidelines of the sample code
>> "MultiSelectTableView". This works as expected.
On Apr 7, 2014, at 20:43 , Michael de Haan wrote:
> I have implemented a custom UITableViewCell in a (test) project with batch
> deletions, following the guidelines of the sample code
> "MultiSelectTableView". This works as expected. However, "swipe to Delete"
> does not work.
> To debug this,
I wonder if I might get some insight into this issue.
I have implemented a custom UITableViewCell in a (test) project with batch
deletions, following the guidelines of the sample code "MultiSelectTableView".
This works as expected. However, "swipe to Delete" does not work.
To debug this, I creat
https://developer.apple.com/library/mac/documentation/Cocoa/Conceptual/ProgrammingWithObjectiveC/EncapsulatingData/EncapsulatingData.html#//apple_ref/doc/uid/TP40011210-CH5-SW3
and scroll up about half a page:
"Properties Are Atomic by Default"
gerd
On Apr 7, 2014, at 6:56 PM, Graham Cox wrot
On 8 Apr 2014, at 6:11 am, Greg Parker wrote:
> No. atomic is the default everywhere.
Do you have a reference for the relevant documentation? I don't know if it's a
reflection on me or Xcode's doc search, but I simply couldn't find it (though
I'm pretty sure I have read it somewhere).
--Gra
On Apr 7, 2014, at 1:52 AM, Kevin Meaney wrote:
> I thought the behaviour was different between iOS and MacOS. On iOS nonatomic
> was the default and atomic on OS X.
No. atomic is the default everywhere.
The only OS difference is that the iOS SDK tends to use nonatomic more than the
OS X SDK.
On 6 Apr 2014, at 2:52 PM, Daniel Luis dos Santos wrote:
> I want to display some text indicating a list of errors the user should
> correct before submitting data.
>
> I am using a modal NSAlert in which i set a message with a localised string
> from a table.
>
> I want to include the error
On Apr 7, 2014, at 03:00 , jonat...@mugginsoft.com wrote:
> I have a function like macro:
>
> #define DBDispatchMonoEvent(KLASS, NAME) \
> do { \
>[DBManagedEvent dispatchEventFromMonoSender:monoSender \
> eventArgs:monoEventArgs \
>
On 07 Apr 2014, at 12:00, jonat...@mugginsoft.com wrote:
> In every case the dispatch macro targets the surrounding class.
> So I would like to reduce the call site invocation to:
>
> static void managedEvent_ItemAdded(MonoObject* monoSender, MonoObject*
> monoEventArgs)
> {
>DBDispatchMono
If in doubt, use protocols.
@protocol MyProtocol
@property NSString *data1;
// …
@end
Then reference the objects as id objects (or
NSOperation)
On Apr 7, 2014, at 22:17, Trygve Inda wrote:
> Hi have three different NSOperation subclasses:
>
> MyOperationA : NSOperation
> MyOperationB : NS
Hi have three different NSOperation subclasses:
MyOperationA : NSOperation
MyOperationB : NSOperation
MyOperationC : NSOperation
Each of my subclasses have a set of 4 required properties:
NSString* data1
NSString* data2
NSString* data3
NSString* data4
Beyond that, my three subclasses are differ
On 2014 Apr 07, at 03:49, Michael Starke
wrote:
> If wanting to build a menu on the fly I've been using the menuNeedsUpdate
> delegate method.
Michael’s advice is correct.
Cocoa Bindings are useful to magically keep visible user interface elements in
sync with data, although the magic comes
No, you can’t. There is no way to accomplish that.
If that is event-based callbacks, try use delegation and/or target-action.
On Apr 7, 2014, at 18:00, jonat...@mugginsoft.com wrote:
> I have a function like macro:
>
> #define DBDispatchMonoEvent(KLASS, NAME) \
> do { \
>[DBManagedEvent dis
If wanting to build a menu on the fly I've been using the menuNeedsUpdate
delegate method. The docs clearly state you can add/remove items this way.
https://developer.apple.com/library/mac/documentation/cocoa/reference/NSMenuDelegate_Protocol/Reference/Reference.html#//apple_ref/occ/intfm/NSMenu
On 7 Apr 2014, at 11:25, Keith J. Schultz wrote:
> Hi Jonny,
>
> try Menu items on the fly!
>
> To my knowledge you can not use IB!
Thanks for your reply keith. I hadn't tried those search terms, but no that
didn't get me anything relevant either. All I could find was one old thread in
which
This must be a very basic question, but I am evidently having difficulty
finding the right search terms. Can anyone point me to some sample code that
will show how to implement a menu whose items are populated at runtime? I would
have expected to be able to bind a menu object to an NSArray consi
I have a function like macro:
#define DBDispatchMonoEvent(KLASS, NAME) \
do { \
[DBManagedEvent dispatchEventFromMonoSender:monoSender \
eventArgs:monoEventArgs \
targetClass:[KLASS class] \
I thought the behaviour was different between iOS and MacOS. On iOS nonatomic
was the default and atomic on OS X.
Kevin
Sent from my iPhone
On 7 Apr 2014, at 05:28, Graham Cox wrote:
>
> On 7 Apr 2014, at 1:58 pm, Ben Kennedy wrote:
>
>> t is for these two reasons that, from years of condi
18 matches
Mail list logo
