On Mar 20, 2011, at 12:45 PM, jonat...@mugginsoft.com wrote:
>
>
> On 20 Mar 2011, at 19:17, Rick Mann wrote:
>
>> I have some code, called from a subclass of NSOperation, that throws an
>> exception pretty reliably if I put a breakpoint elsewhere in the code (it is
>> code that does an HTTP
have you implemented the delegate methods?
is the array mutable? or do you supply a new array that is sorted? do you
reload the data?
On Mar 20, 2011, at 8:44 PM, Lynn Barton wrote:
> I have a document based application. The document window has an NSTableView
> with six columns. Four columns
I have a document based application. The document window has an NSTableView
with six columns. Four columns are bound to four text properties of an entity
in my model; one column is bound to a decimal property, and one column has
check boxes bound to a boolean property. When I run the application
On 20 Mar 2011, at 19:17, Rick Mann wrote:
> I have some code, called from a subclass of NSOperation, that throws an
> exception pretty reliably if I put a breakpoint elsewhere in the code (it is
> code that does an HTTP request, and it's getting a broken pipe, and raising
> an exception to r
I have some code, called from a subclass of NSOperation, that throws an
exception pretty reliably if I put a breakpoint elsewhere in the code (it is
code that does an HTTP request, and it's getting a broken pipe, and raising an
exception to report it; the breakpoint (in another thread) seems to
On Sun, Mar 20, 2011 at 11:59 AM, Quincey Morris
wrote:
> Second, if you're providing a list, you'll have to make sure that you know
> where to find the *current* (i.e. last saved) version of the file, in case
> the file gets saved since the list was constructed. In many cases, the file
> syste
On Mar 20, 2011, at 06:28, Brad Stone wrote:
> After sleeping on it my choices are to remove the encryption feature or make
> a big ugly dialog box warning the user if they encrypt a file that's open
> they will lose their changes. Neither of these approaches are optimum.
On Mar 20, 2011, at 1
If I recall correctly, in iOS 4.0, this was reversed, but the next update
changed the behavior to what we have now.
On Mar 20, 2011, at 1:25 PM, WT wrote:
> I seem to recall that one of the WWDC 2010 instructional videos - available
> for free from Apple's developer site - mentions that the blo
I seem to recall that one of the WWDC 2010 instructional videos - available for
free from Apple's developer site - mentions that the block version has
UIViewAnimationOptionAllowUserInteraction off by default.
That being said, have you filed a document enhancement request?
WT
On Mar 20, 2011, a
Actually, the users are shown files in a NSTableView and they select a menu to
encrypt/decrypt. That's where I'll warn them. Thanks for your suggestion.
On Mar 20, 2011, at 10:10 AM, Robert Martin wrote:
> Given all the problems I've seen raised in this thread, I was just thinking
> that you
That did it.
The "View Programmming Guide for iOS", discusses both methods and implies that
their code samples are equivalent. They don't say, or I didn't see, that the
option you mention is on by default for the begin/commit style and off for the
newer block style.
thanks,
David
On Mar 19
Brad Stone wrote:
On Mar 19, 2011, at 11:04 PM, Brad Stone wrote:
I do need it to work for any app, not just Word or XL.
I guess a poor workaround would be since it's not possible to reliably check if
the file is open>
I can force the user to quit the file's default app before allowing them
On Mar 20, 2011, at 9:28 AM, Brad Stone wrote:
> After sleeping on it my choices are to remove the encryption feature or make
> a big ugly dialog box warning the user if they encrypt a file that's open
> they will lose their changes. Neither of these approaches are optimum.
Are you sure you n
After sleeping on it my choices are to remove the encryption feature or make a
big ugly dialog box warning the user if they encrypt a file that's open they
will lose their changes. Neither of these approaches are optimum.
On Mar 19, 2011, at 11:04 PM, Brad Stone wrote:
> I do need it to work f
On Mar 19, 2011, at 9:44 PM, Luke Evans wrote:
> I'm curious as to the best (or a) way to achieve the following:
>
> - I have a Core Data model set up with validation of various kinds
> (non-optional values, ranges, regexs etc.) on attributes.
> - I have a table based UI showing these entities f
On Mar 19, 2011, at 16:17, Darren Wheatley wrote:
> I have the default out-of-the-box sorting working, but when I click one of
> the column headers to sort the table I have problems.
Looks like you didn't get any takers on this yet.
TBH, I have no idea what "default out-of-the-box sorting" means
On Mar 20, 2011, at 00:48, Luke Evans wrote:
> However, my original query was motivated by general curiosity as to whether
> the Core Data constraints could readily be surfaced to bound UI in some way,
> without the whole error mechanism that goes with the validate protocol,
> and indeed the wa
Thanks Quincey and Jerry for the responses.
I was fishing for whether there was a clever Cocoa/Core Data way to get
'friendly' validation warnings like UI highlighting automatically propagated
up to the UI from the existing managed object properties without a lot of
extra coding overhead. Cocoa b
18 matches
Mail list logo
