date:20080602

Re: File still in use after closing document window

2008-06-02 Thread Antonio Nunes


On Jun 3, 2008, at 8:46 AM, Bill Bumgarner wrote:


The actual loading is done like this:

		self.masterPDFDocument = [[ANPDFDocument alloc] initWithURL:  
absoluteURL];


If your -setMasterPDFDocument: -- synthesized or manually written --  
follows traditional reatain/release rules, the above will result in  
the ANPDFDocument being over-retained.


The masterPDFDocument ivar is indeed a synthesized property, but the  
app is garbage collected, so I would expect the reference to be  
collected shortly after its host document is closed.


António

-
Forgiveness is not an occasional act;
it is a permanent attitude.

--Martin Luther King, Jr
-




___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to [EMAIL PROTECTED]

Re: File still in use after closing document window

2008-06-02 Thread Bill Bumgarner


On Jun 2, 2008, at 10:57 PM, Antonio Nunes wrote:

The actual loading is done like this:

		self.masterPDFDocument = [[ANPDFDocument alloc] initWithURL:  
absoluteURL];


If your -setMasterPDFDocument: -- synthesized or manually written --  
follows traditional reatain/release rules, the above will result in  
the ANPDFDocument being over-retained.


b.bum
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to [EMAIL PROTECTED]

CoreData file format stability

2008-06-02 Thread Charles Srstka

Okay, after many years of pretty much only doing software that had to  
run on very old versions of Mac OS X, I've finally decided to do some  
stuff that might require Tiger or maybe even Leopard, so I've been  
able to start exploring some of the various new features Cocoa has  
picked up over the years, such as bindings and such. Now, I'm having a  
look at CoreData. It looks neat, but I do have a couple of questions/ 
concerns about it. The first of these is:


1) The file format for saved files. I'd rather not make some  
proprietary/closed Microsoft-ish thing - I'd like it to be possible  
for other programs to read/write my file format, including  
hypothetical programs that might get written for other platforms so  
that my file format could possibly be readable and writable by our  
Linux friends (and Windows carbon units as well). Since CoreData has a  
SQLite-based format, and since SQLite is available pretty much  
everywhere, this seems pretty good as long as I am able to figure out  
how CoreData sets up the tables and such in its documents, except for  
one concern: what if the layout of the SQLite file CoreData creates  
changes? If CoreData on 10.6, 10.7, etc. all generate SQLite files  
that are set up a bit differently from the way the previous version of  
OS X did it, that could create a very annoying moving target for  
anyone trying to access the files via a non-CoreData means. Now, one  
would think that would not be likely to happen, since it could  
potentially cause a very confusing situation where the same exact  
binary would create a different file format depending on which OS  
version it was running on, but then again this *is* Apple we're  
talking about, so I'm a little paranoid. Is there any documentation  
anywhere promising that the format of the CoreData save files won't  
change in future versions of the OS, or failing that, could one of the  
Apple employees here let me know if this is a valid concern or not?


2) Is CoreData able to edit files in place at all? The reason I am  
asking is because the documents my hypothetical app would work with  
could possibly become very large, maybe even in the 300-400 MB range.  
Would CoreData be able to just open the files, let me search them, add  
stuff to them, etc., like one would normally be able to do just by  
using SQLite directly, or would it be copying the whole thing into a  
store file somewhere or into RAM every time a file is opened?


Basically what I need to do at this stage is determine whether  
CoreData is suitable for my hypothetical app, or whether I should just  
roll something myself using the SQLite3 APIs directly. As always, any  
help is greatly appreciated.


Thanks,
Charles
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to [EMAIL PROTECTED]

Re: File still in use after closing document window

2008-06-02 Thread Antonio Nunes


On Jun 2, 2008, at 2:06 PM, Hamish Allan wrote:


My NSDocument based app loads (imports) PDF files into its documents.


What code are you using to load them?


The actual loading is done like this:

		self.masterPDFDocument = [[ANPDFDocument alloc] initWithURL:  
absoluteURL];


Although I doubt it would have any influence: Before loading I also  
make sure the document ends up in the recent documents menu, since  
some trickery is involved to get all the openable files to show up in  
that place:


		// We want the original doc URL to be added to the recent menu  
BEFORE we change the URL to our native file type.

if (! loadedFromBundle) {
			[[NSDocumentController sharedDocumentController]  
noteNewRecentDocumentURL:[self fileURL]];

}

-António


There is a world of difference between
searching for happiness and choosing
to be happy.





___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to [EMAIL PROTECTED]

Re: Hillegass book memory question

2008-06-02 Thread Adam Leonard


Hi,
I have the second edition still, but I assume this example has not  
changed much in the third edition.


Usually, yes, you must release anything you +alloc, -retain, -copy,  
etc. This is a bit of a special case though.


In this case, exactly one NSSpeechSynthesizer is allocated when the  
application is launched (in AppController's -init), and it is used for  
almost the entire life of the application; i.e., the same speech  
synthesizer is always used whenever one of the buttons is pressed  
until the user quits the application.
However, the operating system will always reclaim all memory you  
malloc'd when the application quits. It just takes the entire memory  
space your application used and say it is "free" for other  
applications to use.


So, it is very common to take advantage of this fact. The speech  
synthesizer object is automatically dealloc'd by the OS very soon  
after you are done using it, so there is no reason to explicitly  
release it yourself.

The Cocoa frameworks take this shortcut, as do most applications.

By the way, this shortcut is not just the result of laziness, it is  
actually faster. Instead of going through all the objects that are  
used throughout the life span of the app, and having the OS free all  
of them one at a time, the shortcut lets the OS group all these  
objects and free them at the same time.


It is, however, perfectly acceptable to override -dealloc in  
AppController and call [speachSynthesizer release]. I am sure this is  
discussed elsewhere in the book.



Hope that makes sense.

Adam Leonard

On Jun 2, 2008, at 9:39 PM, Ashley Perrien wrote:

I'm working my way through the 3rd edition and have a question  
specifically on speech synthesizer in chapter 5. It's my  
understanding that whenever something is retained or alloced they  
eventually need to be released. In the application built in the  
chapter, NSSpeechSynthesizer is alloced and an array is retained and  
neither are released. I know that for the very small and simple apps  
here, it doesn't really matter but how and where would you go about  
releasing those objects? If they shouldn't be released, why not?


Thanks for any enlightenment.

Ashley Perrien
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/adam%40caffeinatedcocoa.com

This email sent to [EMAIL PROTECTED]



___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to [EMAIL PROTECTED]

Re: Main window disappears. Sometimes.

2008-06-02 Thread Michael Ash

On Tue, Jun 3, 2008 at 10:47 AM, William Bumgarner <[EMAIL PROTECTED]> wrote:
> Certainly, there could be better support -- a better out of the box pattern 
> -- for dealing with the loading of auxiliary nibs.

NSWindowController and NSViewController handle approximately the
totality of auxiliary nib-loading needs. I would go so far as to say
that if you have a nib which doesn't fit into one of those two, you're
doing something wrong and should rebuild it. The problem with them is
simply that many people don't know about them, or don't know how to
use them. It took me a couple of years before I really realized that
every window should have its own NSWindowController which loads the
nib for that one window. Once I figured it out, life got a lot easier.

Mike
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to [EMAIL PROTECTED]

Solved (still open to suggestions): DTrace probe problem

2008-06-02 Thread radj

Finally got it to poll. I had to study signals and signal handling within
the driver. lol. I've tried it and atleast it helps me delay the actual
"initialization" of the driver while I run the D script.

Your quick responses were really helpful. Thanks alot, Bill!

DTrace rocks!

radj

On Mon, Jun 2, 2008 at 10:31 AM, Bill Bumgarner <[EMAIL PROTECTED]> wrote:

> On Jun 1, 2008, at 7:19 PM, radj wrote:
>
>> I can try that. Sounds like a good idea. Make the "waiting for the signal"
>> the first thing the driver will do. but how do you send a signal from within
>> DTrace to a specific process?
>>
>
> I have no idea if dtrace can send a signal.   I would send a kill -USR1 via
> a shell command...
>
> b.bum
>
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to [EMAIL PROTECTED]

Re: Key-Value pairs

2008-06-02 Thread Michael Ash

On Tue, Jun 3, 2008 at 5:41 AM, Hamish Allan <[EMAIL PROTECTED]> wrote:
> On Mon, Jun 2, 2008 at 10:30 PM, john darnell
> <[EMAIL PROTECTED]> wrote:
>
>> I just read Hillegass' chapter that introduces Key-Value coding.
>
>>  My question is, if this is such a necessary thing, why didn't the
>> designers simply design the compiler to auto-generate setter and getter
>> functions as per the requisite style in the first place?
>
> I haven't read Hillegaas' latest book, but perhaps in a less
> introductory chapter he will go on to talk about @synthesise, which
> does exactly what you're looking for.

Also even without @synthesize, KVC will work just fine with no
accessors present. The KVC implementation will happily extract the
value directly from your instance variable by using its name, or put a
new value into it.

Mike
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to [EMAIL PROTECTED]

Hillegass book memory question

2008-06-02 Thread Ashley Perrien

I'm working my way through the 3rd edition and have a question  
specifically on speech synthesizer in chapter 5. It's my understanding  
that whenever something is retained or alloced they eventually need to  
be released. In the application built in the chapter,  
NSSpeechSynthesizer is alloced and an array is retained and neither  
are released. I know that for the very small and simple apps here, it  
doesn't really matter but how and where would you go about releasing  
those objects? If they shouldn't be released, why not?


Thanks for any enlightenment.

Ashley Perrien
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to [EMAIL PROTECTED]

Re: Getting started with Core Animation

2008-06-02 Thread Matt Long

Hey Graham. I wrote a blog post not too long ago that demonstrates  
adding layers to a root layer. You can see it here: http://www.cimgf.com/2008/03/15/core-animation-tutorial-dashboard-effect/


I think you want to get the root content layer and then call  
insertSublayer or addSublayer to it. Here's what I do in the  
awakeFromNib in that blog post:


-(void)awakeFromNib;
{
[[window contentView] setWantsLayer:YES];
[window setFrame:[[NSScreen mainScreen] frame] display:NO  
animate:NO];


NSRect contentFrame = [[window contentView] frame];
CALayer *root = [[window contentView] layer];

// mainLayer is the layer that gets scaled. All of its sublayers
// are automatically scaled with it.
mainLayer = [CALayer layer];
mainLayer.frame = NSRectToCGRect(contentFrame);

// Make the background color to be a dark gray with a 50% alpha  
similar to

// the real Dashbaord.
mainLayer.backgroundColor = CGColorCreateGenericRGB(0.10, 0.10,  
0.10, 0.50);

[root insertSublayer:mainLayer above:0];

// Add a new layer to the mainlayer.
[self addNewLayer:nil];

scaleUp = YES;
}

You can get my demo project from here: 
http://www.cimgf.com/wp-content/uploads/2008/03/dashboardeffect.zip

HTH

-Matt



On Jun 2, 2008, at 9:51 PM, Graham Cox wrote:


Hi all,

I'm looking at Core Animation for the first time. Having a bit of  
trouble getting started with the simplest set-up I can imagine.


Goal - to add a single CALayer in my view so I can see it. Then, try  
some simple animations. I've tried a few different things but I just  
can't see any visible trace of my layer. Here's the code, part of my  
custom view (actually, almost all of it):


- (id)  initWithFrame:(NSRect)frame
{
   self = [super initWithFrame:frame];
   if (self)
{
CALayer* rootLayer = [CALayer layer];

theLayer = [CALayer layer];

CGRect  frame = {10,10,110,150};
CGColorRef  bk = CGColorCreateGenericRGB( 0.5, 0.5, 0, 1.0 
);

[theLayer setCornerRadius:10.0];
[theLayer setBorderWidth:4.0];
[theLayer setFrame:frame];
[theLayer setBackgroundColor:bk];

[rootLayer addSublayer:theLayer];

[self setLayer:rootLayer];
[self setWantsLayer:YES];

CGColorRelease( bk );
   }
   return self;
}


n.b. 'theLayer' is an ivar.

Initially I didn't have a separate rootLayer, but looking at some  
sample code it seems most code uses one. Even though there's no  
layer content set I should see the border and the background colour  
shouldn't I? What am I missing?


BTW, another things that's a little unclear - when the rootLayer is  
added to the view, does it adopt the view's frame? Or should I be  
setting this explicitly? Sample code appears to just let it use its  
defaults.



thanks for any insight,


Graham
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/matt.long%40matthew-long.com

This email sent to [EMAIL PROTECTED]


___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to [EMAIL PROTECTED]

A little extra cash...

2008-06-02 Thread J. Todd Slack


Hi All,

I am willing to pay a small sum (since I am an NPO) for someone who  
can create a small example all that creates as NSStatusMenu, fills it  
with a menu items and shows me how to call code (objective-C And  
AppleScript) when a menu option is selected.


Who is up to do this?

$100.00 sound OK?

I am missing something and would like a great example.

Stipulations main must be a .c so I can create an iTunesPlugin.

I started this here: 
http://thejasonandannettefoundation.org/public/jason/Ring-Maker-Plugin.zip

Hit em up..
-Jason
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to [EMAIL PROTECTED]

Getting started with Core Animation

2008-06-02 Thread Graham Cox


Hi all,

I'm looking at Core Animation for the first time. Having a bit of  
trouble getting started with the simplest set-up I can imagine.


Goal - to add a single CALayer in my view so I can see it. Then, try  
some simple animations. I've tried a few different things but I just  
can't see any visible trace of my layer. Here's the code, part of my  
custom view (actually, almost all of it):


- (id)  initWithFrame:(NSRect)frame
{
self = [super initWithFrame:frame];
if (self)
{
CALayer* rootLayer = [CALayer layer];

theLayer = [CALayer layer];

CGRect  frame = {10,10,110,150};
CGColorRef  bk = CGColorCreateGenericRGB( 0.5, 0.5, 0, 1.0 
);

[theLayer setCornerRadius:10.0];
[theLayer setBorderWidth:4.0];
[theLayer setFrame:frame];
[theLayer setBackgroundColor:bk];

[rootLayer addSublayer:theLayer];

[self setLayer:rootLayer];
[self setWantsLayer:YES];

CGColorRelease( bk );
}
return self;
}


n.b. 'theLayer' is an ivar.

Initially I didn't have a separate rootLayer, but looking at some  
sample code it seems most code uses one. Even though there's no layer  
content set I should see the border and the background colour  
shouldn't I? What am I missing?


BTW, another things that's a little unclear - when the rootLayer is  
added to the view, does it adopt the view's frame? Or should I be  
setting this explicitly? Sample code appears to just let it use its  
defaults.



thanks for any insight,


Graham
___

Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to [EMAIL PROTECTED]

Re: trying to glue a cocoa ui to a pthread application / subclassing nsview

2008-06-02 Thread Quincey Morris

On Jun 2, 2008, at 19:49, Michael Toy wrote:

what I find is that my initWithFrame method is not being called ...
so i have two questions ...

my drawRect: IS being called, so I know my custom view is being
instantiated. why is my init not being called? i thought i figured
out the documentaiton enough to understand that the phrase "This
method is the designated initializer for the NSView class. Returns
an initialized object." meant that this was the only method i needed
to write to have custom behavior at creation time.

forget that, is there another way to win?

thanks in advance, i am happy to accept pointers to the
documentation i should have found.

If you designed your view in IB, so that it's in a nib file,
initWithFrame is not necessarily called when your application runs.
(initWithCoder may be called instead.) See:

http://developer.apple.com/documentation/Cocoa/Conceptual/CocoaViewsGuide/SubclassingNSView/chapter_6_section_2.html#/
/apple_ref/doc/uid/TP40002978-CH7-SW20

1 2 >

1 - 100 of 102 matches

Mail list logo