On 17 Sep 2013, at 00:26, Graham Cox wrote:
>
> What I was sort of hoping was that there was a way to figure out from the
> archive how many objects there were without having to archive the number
> explicitly. For example, the root level of an archive is a dictionary, which
> has a count, b
On 2013 Sep 16, at 08:53, Graham Cox wrote:
If I wanted to add some sort of progress reporting to archiving and
dearchiving, what's a good way to do it? The problem seems to me to
know what the 'count' of things read from/written to the file is to
set the progress max value. Since the delegate
On Sep 16, 2013, at 11:33 AM, "Gerriet M. Denkmann"
wrote:
> I also did some more testing. The magic does not lie in the NSLog() but in
> the elapsed time.
>
> On my machine the sending of a message to remoteObjectProxy must NOT be done
> earlier than ca. 180 μsec after [NSXPCConnection resum
On 16 Sep 2013, at 23:13, Keary Suska wrote:
>
> On Sep 16, 2013, at 9:27 AM, Gerriet M. Denkmann wrote:
>
>>
>> On 16 Sep 2013, at 22:21, Charles Srstka wrote:
>>
>>> On Sep 16, 2013, at 10:16 AM, "Gerriet M. Denkmann"
>>> wrote:
>>>
If (and only if) MAGIC_BUG_REMOVAL is defined, I
On 16 Sep 2013, at 23:16, Charles Srstka wrote:
> On Sep 16, 2013, at 10:27 AM, "Gerriet M. Denkmann"
> wrote:
>
>> Maybe I was not very clear.
>> The problem is NOT that the helper app does not start. There just is no
>> helper app, there is nothing which has a MachService called
>> "somet
On 16 Sep 2013, at 22:21, Charles Srstka wrote:
> On Sep 16, 2013, at 10:16 AM, "Gerriet M. Denkmann"
> wrote:
>
>> If (and only if) MAGIC_BUG_REMOVAL is defined, I see:
>> Error Domain=NSCocoaErrorDomain Code=4099 "Couldn’t communicate with a
>> helper application."
>>
>> Makes sense, as t
On 16/09/2013, at 4:25 PM, Chris Devereux wrote:
> How about tracking the number of written objects when saving the document,
> then encoding an additional key containing the object count at the top
> level of the archive? This could then be retrieved before decoding the root
> object.
>
> A po
On Sep 16, 2013, at 10:16 AM, "Gerriet M. Denkmann"
wrote:
> If (and only if) MAGIC_BUG_REMOVAL is defined, I see:
> Error Domain=NSCocoaErrorDomain Code=4099 "Couldn’t communicate with a helper
> application."
>
> Makes sense, as there just is no helper application named:
> "something.very.s
On 16 Sep 2013, at 22:13, Charles Srstka wrote:
> On Sep 16, 2013, at 3:22 AM, Gerriet M. Denkmann wrote:
>
>> ree =[ aCo remoteObjectProxyWithErrorHandler: ^(NSError *err)
>> {
>> // if helperName is not running
>
Another angle worth looking at: Depending on the output format you're using
with NSKeyedArchiver, your file might already contain an object count, even
if the API doesn't expose it.
According to the Cocotron source[1], the binary plist format actually does
this. It won't correspond exactly to the
On Sep 16, 2013, at 12:24 PM, Kevin Perry wrote:
> Re-using a single NSDocument instance to represent several different files is
> certainly atypical…
True, and I don't know what other similar applications so, but for some
applications that are viewers it makes sense to let the user move forw
On 16/09/2013, at 6:51 PM, Jeffrey Oleander wrote:
> I'll bite. If you want to know the total number of objects to be archived,
> then you need to count them, at some time or another. To count them, you
> need to walk the object tree before you start actually archiving... which
> may take
On 16/09/2013, at 8:08 PM, Jeffrey Oleander wrote:
> Yes, of course, you can. But that is too late.
> You need to know the total, the max, before you display the progress bar
Ah, true but in fact displaying progress when dearchiving is more important.
Documents get saved in the background, s
Re-using a single NSDocument instance to represent several different files is
certainly atypical…
But, I suspect the problem here is that you're not using File Coordination when
reading in the contents of the new file. By not doing that, you're not giving
File Coordination the hint that it need
Hey guys I'm really grinding with the NSCollectionView when its bound. I had a
running collection view but wanted to use bindings, I looks like it should
work, but it doesn't. This is written just in code not in IB.
Hope you guys can help :)
The problem is, the View is displayed correctly,
On Sep 16, 2013, at 10:27 AM, "Gerriet M. Denkmann"
wrote:
> Maybe I was not very clear.
> The problem is NOT that the helper app does not start. There just is no
> helper app, there is nothing which has a MachService called
> "something.very.silly".
>
> The problem is, that the error block,
On Sat, Sep 14, 2013, at 01:14 PM, Brian Clark wrote:
> I'm hoping someone can suggest the correct way to deal with the following
> problem.
>
> For an image viewing app i display a file in the usual way in an
> NSDocument. setFileURL: is properly called by NSDocument's
> _initWithContentsOfURL:of
On Sep 16, 2013, at 4:38 AM, Mike Abdullah wrote:
>
> On 14 Sep 2013, at 21:14, Brian Clark wrote:
>
>> I'm hoping someone can suggest the correct way to deal with the following
>> problem.
>>
>> For an image viewing app i display a file in the usual way in an NSDocument.
>> setFileURL: is
On Sep 16, 2013, at 9:27 AM, Gerriet M. Denkmann wrote:
>
> On 16 Sep 2013, at 22:21, Charles Srstka wrote:
>
>> On Sep 16, 2013, at 10:16 AM, "Gerriet M. Denkmann"
>> wrote:
>>
>>> If (and only if) MAGIC_BUG_REMOVAL is defined, I see:
>>> Error Domain=NSCocoaErrorDomain Code=4099 "Couldn’t
On Sep 16, 2013, at 3:22 AM, Gerriet M. Denkmann wrote:
> ree = [ aCo remoteObjectProxyWithErrorHandler: ^(NSError *err)
> {
> // if helperName is not running
> (always the case) and
>
On 16 Sep 2013, at 22:10, Charles Srstka wrote:
> On Sep 16, 2013, at 3:22 AM, Gerriet M. Denkmann wrote:
>
>> In a new app (not document based) I inserted:
>>
>> #import "ZipProtocol.h"
>>
>> // ZipProtocol.h:
>> @protocol ZipProtocol
>> - (void)command:(NSString *)command withReply: (v
On Sep 13, 2013, at 1:27 PM, Rich Collyer wrote:
> I am looking at at view that covers the entire iPhone screen. The app is also
> required to only work in Landscape. I see that in viewWillAppear the bounds
> and center of the view are in Portrait mode - this is fine. However, in
> viewDidApp
How about tracking the number of written objects when saving the document,
then encoding an additional key containing the object count at the top
level of the archive? This could then be retrieved before decoding the root
object.
A possible problem with this idea is that it might require the data
Hi all,
If I wanted to add some sort of progress reporting to archiving and
dearchiving, what's a good way to do it? The problem seems to me to know what
the 'count' of things read from/written to the file is to set the progress max
value. Since the delegate gets called for each object instanti
On Sep 16, 2013, at 9:12 , Uli Kusterer wrote:
> On 16 Sep 2013, at 01:10, Greg Parker wrote:
>> And of course every Cocoa app halts by calling exit(). NSApplicationMain()
>> never returns. (I'm pretty sure it doesn't attempt to stop the main run
>> loop, either.)
>
> It does go and close al
On 14 Sep 2013, at 21:14, Brian Clark wrote:
> I'm hoping someone can suggest the correct way to deal with the following
> problem.
>
> For an image viewing app i display a file in the usual way in an NSDocument.
> setFileURL: is properly called by NSDocument's
> _initWithContentsOfURL:ofTyp
I'm hoping someone can suggest the correct way to deal with the following
problem.
For an image viewing app i display a file in the usual way in an NSDocument.
setFileURL: is properly called by NSDocument's
_initWithContentsOfURL:ofType:error:.
I now want to display the next file in the folder
I am looking at at view that covers the entire iPhone screen. The app is also
required to only work in Landscape. I see that in viewWillAppear the bounds and
center of the view are in Portrait mode - this is fine. However, in
viewDidAppear the bounds of the view are in Landscape, but the center
I'm writing a signal processing program and I am trying to use a window to
display multiple NSViews of an oscilloscope, histograms, etc. I create the
NSTabViewItems programmatically. The window controller declares the following
properties:
@property(nonatomic, strong) IBOutlet NSWindow
On 02 Sep 2013, at 18:42, Graham Cox wrote:
> Maybe more education is needed but we thought we had explained all that.
> Maybe we need to display the calculated pixel sizes up front so the user
> doesn't get surprised by the outcome.
I’d go with the latter. If a popular app or the system displ
Thanks Kyle and Jerry.
It feels a bit strange to be adding extra glue code to track
otherwise-completely-autonomous windows (and controllers), but that has
certainly done the trick.
I found the static analyzer a bit odd to get used to - it sometimes gives
purportedly very detailed explanations
In a new app (not document based) I inserted:
#import "ZipProtocol.h"
// ZipProtocol.h:
@protocol ZipProtocol
- (void)command:(NSString *)command withReply: (void (^)( NSString
*answerString ))reply;
@end
#define MAGIC_BUG_REMOVAL // defined or not - makes a strange
diff
On 16 Sep 2013, at 01:10, Greg Parker wrote:
> And of course every Cocoa app halts by calling exit(). NSApplicationMain()
> never returns. (I'm pretty sure it doesn't attempt to stop the main run loop,
> either.)
It does go and close all documents and send
NSApplicationWillTerminateNotificati
33 matches
Mail list logo
