date:20101018

Re: NSSavePanel does replace / in the filename with a :

2010-10-18 Thread Thorsten Lemke

Hi,
 
Ah - I convert the : now manually to a / for the following File Manger Calls
(not Cocoa). That does it.

Thorsten
> 
>> The problem is: 
>> I enter as name i.e.: Part 1/2.jpg into the save panel.
>> I click on ok.
>> I get as filename in the code: "Part 1:2.jpg".
>> 
>> So, how can I avoid this?
> 
> You don't avoid it.  You don't want to.
> 
> The *user-visible* file name is "Part 1/2.jpg".
> 
> The correct *internal representation* of that file name is "Part 1:2.jpg".
> 
> There's no reason for the internal representation to be the same as the
> user-visible name.  You shouldn't care what the internal representation is.
> And the user should never see it.  When you need to present a file name to the
> user, you use the methods I mentioned previously to obtain the appropriate
> user-visible display name.  But other than that, you should be working with
> the internal representation.
> 
> Regards,
> Ken
> 


___

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 arch...@mail-archive.com

Re: NSSavePanel does replace / in the filename with a :

2010-10-18 Thread Uli Kusterer

On 18.10.2010, at 09:54, Thorsten Lemke wrote:
> Ah - I convert the : now manually to a / for the following File Manger Calls
> (not Cocoa). That does it.

 What are you doing? Are you trying to read old preferences that contain Carbon 
paths? This should *not* be necessary.

-> If you're displaying file names to the user, use displayNameAtPath:. Not 
only does it substitute slashes for colons as needed, it also honors hidden 
file extensions, and shows localized names for folders on non-English operating 
systems. And componentsToDisplayForPath: will correctly add the hard disk name 
at the start, or remove /Volumes, just like the Finder does.

-> If you're accessing files, you can simply pass this "wrong" path with the 
colon in it to any POSIX or Cocoa call and it'll work.

-> If you're converting between POSIX/Cocoa paths and CoreServices file manager 
paths, use the existing conversion calls. CFURLRef includes some neat methods 
to let you convert between both kinds of paths. In any case, Apple's 
recommended format handling file paths is CFURLRef/NSURL*. Speaking in Carbon 
terms, that class wraps information not unlike an FSRef inside it, so it's a 
much faster and more efficient way of storing file references than paths (at 
least on 10.6 and later, where this actually got implemented). You can even get 
back alias-like data for storing on disk by grabbing the "bookmark data" from a 
NSURL.

Cheers,
-- Uli Kusterer
"The Witnesses of TeachText are everywhere..."
http://www.zathras.de

___

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 arch...@mail-archive.com

Re: remove icon from Dock

2010-10-18 Thread Uli Kusterer

On Oct 13, 2010, at 5:57 AM, Kyle Sluder wrote:
> Meanwhile, iWork 09's installer does this very thing. It adds its
> icons to the dock and then quits it.

 Quod licet Iovi, non licet bovi.

 'nuff said.

Cheers,
-- Uli Kusterer
"The Witnesses of TeachText are everywhere..."



___

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 arch...@mail-archive.com

Image Resolution

2010-10-18 Thread Amy Heavey


Hi,

I've got an app that generates composite images, so it places images  
onto a single canvas and saves that as a new image. It's working fine,  
but I'm struggling with the resolutions/representations issue.


The source images are not generated by us, they are from a variety of  
surces, and are generally 200pixels + on each side, however sometimes  
they are 72 dpi, and sometimes they are 300dpi. Even if an aimage is  
450pixels square, when it is set as 300 dpi it's reduced too small  
when my app reduces it it to fit a 75pixel square area.


I know this is to do with the bitmapRepresentation, but I can't work  
out how to change it. If I was doing this in photoshop I'd be keeping  
the actual pixel count, but changing the resolution from 300 to 72 for  
these images.


Can anyone point me in the right direction?  Here's the code I'm using  
at the moment:


while ((imgPath = [imageLoop nextObject])) {
NSImage *img = [[NSImage alloc]initWithContentsOfFile:imgPath];
[targetImage lockFocus];

		[img drawInRect:NSMakeRect(x,y,75,75) fromRect:NSMakeRect(20,20,0,0)  
operation:NSCompositeCopy fraction:1];



Thanks

Amy Heavey
___

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 arch...@mail-archive.com

NSArrayController making copies of my objects?

2010-10-18 Thread Trygve Inda

I am trying to figure out exactly what is happening here.

I have a mutable dictionary where each object is also an NSMutableDictionay
containing 9 string objects.

NSMutableDictionary*  myData;// this is in MyController object.

In a window, I have an NSTableView whose column data is tied to an
NSArrayController. The NSArrayController is bound to myData with IB:

Bind to MyController, keypath: myda...@allvalues

This all works fine, except

I would expect the following to have the same addresses:

NSMutableDictionary*myItemA =
[[[MyController myData] allValues] objectAtIndex:0];

NSMutableDictionary*   arrayContItemA =
[[myArrayController arrangedObjects] objectAtIndex:0];

The content is the same (the 9 strings) so it is coming from the right
place, but the addresses of the objects are different so for some reason the
NSArrayController is making a copy of my dictionary object somewhere along
the line.

I understand that the array returned by allValues is not mutable so the
NSArrayController may need to make a mutable copy of it, but the internal
objects are mutable... So why is it copying my objects?

If I add the following just before the above two lines, then the objects
have the same address as expected.

[MyController willChangeValueForKey:@"myData"];
[MyController didChangeValueForKey:@"myData"];

So I gather this is forcing the NSArrayController to write it's
copied/cached values back to myData.

The point is that I need to be able to edit the items in the NSTable, then
write myData back to disk and have the changes be saved. If I never call
will/didChangeValueForKey, then the changes are lost.

Since I am not changing myData directly but it is being changed by the
NSTableView and NSArrayController, why does this happen this way?

Thanks,

Trygve


___

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 arch...@mail-archive.com

Re: Codesign additional items within an app bundle

2010-10-18 Thread Jerry Krinock


On 2010 Oct 17, at 07:53, Michael Diehr wrote:

> Taking my first stab at codesigning an OS X App, and I'm noticing that only 
> some items within the app bundle get signed

Didn't read all of your message, but looks like you probably need the same 
answer I got last year…

http://lists.apple.com/archives/Apple-cdsa/2009/May/msg00031.html

Also, you've got the wrong mailing list for this question.  Post any further 
discussion to Apple CDSA .

___

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 arch...@mail-archive.com

CMYK Text of Photoshop Layer rendered incorrectly

2010-10-18 Thread Peter Krajčík

Hi,
 
I am reading Photoshop layer images using this approach:
 
(simplified code)
 
for (i=0; i <= imageCount; i++)
{
unsigned long offset, size;
GraphicsImportSetImageIndex(importer, i);
GraphicsImportGetDataOffsetAndSize(importer, &offset, &size);
 
// create a Graphics Exporter component that will write Photoshop data
OSErr err = 
OpenADefaultComponent(GraphicsExporterComponentType,kQTFileTypePhotoShop, 
&exporter);
 
if (err == noErr)
{
 // set export parameters
 Handle bmpDataH = NewHandle(0);
 GraphicsExportSetInputGraphicsImporter(exporter, importer);
 GraphicsExportSetOutputHandle(exporter, bmpDataH);
 
 // export data to BMP into handle
 unsigned long actualSizeWritten = 0;
 err = GraphicsExportDoExport(exporter, &actualSizeWritten);
 
  if (err == noErr)
  {
 
   HLock(bmpDataH);
 
   //create a simple image with the tiff data, without the bound 
information, its rep will stored to layer as CGImageRef
   id image = [CIImage imageWithData:[NSData 
dataWithBytes:*bmpDataHlength:GetHandleSize(bmpDataH)]];
   NSBitmapImageRep* rep = [[[NSBitmapImageRep alloc] 
initWithCIImage:image]autorelease];
 
   CGImageRef imageRef = rep.CGImage;
   self.layerImage =CGImageRetain(imageRef);
   HUnlock(bmpDataH);
 }
 
 DisposeHandle(bmpDataH);
 CloseComponent(exporter);
 }
 
}
 
It works as expected, but when I open a psd file that has layers with TEXT (not 
rendered) and in CMYK color space, it looks like alpha channel of such layer is 
igonred and I'm getting a black rect instead (with text on top of it).
 
I have read in some old post (2005) that is is a bug in Apple importer. 
The fact is that I didn't find other way how to read in images from psd files.
 
A. Is there any tip how to fix the CMYK-TEXT alpha problem I described ?
B. Is there any other way how to read photoshop layer images ?
 
Thank you.
 
Peter___

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 arch...@mail-archive.com

Re: CMYK Text of Photoshop Layer rendered incorrectly

2010-10-18 Thread Thorsten Lemke

Hi Peter,

I suggest to use the Core Image Import:
CGImageSourceRef imageSource =
CGImageSourceCreateWithURL((CFURLRef)[NSURL fileURLWithPath:path],
NULL);


That does handle CMYK, too.

Thorsten


> Von: Peter Krajčík 
> Datum: Mon, 18 Oct 2010 14:53:10 +0200
> An: 
> Betreff: CMYK Text of Photoshop Layer rendered incorrectly
> 
> Hi,
>  
> I am reading Photoshop layer images using this approach:
>  
> (simplified code)
>  
> for (i=0; i <= imageCount; i++)
> {
> unsigned long offset, size;
> GraphicsImportSetImageIndex(importer, i);
> GraphicsImportGetDataOffsetAndSize(importer, &offset, &size);
>  
> // create a Graphics Exporter component that will write Photoshop data
> OSErr err = 
> OpenADefaultComponent(GraphicsExporterComponentType,kQTFileTypePhotoShop,
> &exporter);
>  
> if (err == noErr)
> {
>  // set export parameters
>  Handle bmpDataH = NewHandle(0);
>  GraphicsExportSetInputGraphicsImporter(exporter, importer);
>  GraphicsExportSetOutputHandle(exporter, bmpDataH);
>  
>  // export data to BMP into handle
>  unsigned long actualSizeWritten = 0;
>  err = GraphicsExportDoExport(exporter, &actualSizeWritten);
>  
>   if (err == noErr)
>   {
>  
>HLock(bmpDataH);
>  
>//create a simple image with the tiff data, without the bound
> information, its rep will stored to layer as CGImageRef
>id image = [CIImage imageWithData:[NSData
> dataWithBytes:*bmpDataHlength:GetHandleSize(bmpDataH)]];
>NSBitmapImageRep* rep = [[[NSBitmapImageRep alloc]
> initWithCIImage:image]autorelease];
>  
>CGImageRef imageRef = rep.CGImage;
>self.layerImage =CGImageRetain(imageRef);
>HUnlock(bmpDataH);
>  }
>  
>  DisposeHandle(bmpDataH);
>  CloseComponent(exporter);
>  }
>  
> }


___

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 arch...@mail-archive.com

Re: Heapshot Analysis to find Memory Accretion (Leaks)

2010-10-18 Thread Roland King

To my Cocoa Keepers file. 

Bill thank you very much, I didn't know what Heapshot did and what the output 
meant. Now I do. 



On 18-Oct-2010, at 11:52 AM, Bill Bumgarner wrote:

> Folks--
> 
>   I wrote up an article on how to use the "Mark Heap" / "Heapshot 
> Analysis" tools in Instruments to detect, analyze, and fix memory leaks, 
> including those that leaks can't find.
> 
>   
> http://www.friday.com/bbum/2010/10/17/when-is-a-leak-not-a-leak-using-heapshot-analysis-to-find-undesirable-memory-growth/
> 
>   I would encourage everyone to give it a spin with your app.  If it is 
> document based, then:
> 
>   - launch your app under Instruments with the Allocations Instrument
>   - (1) open a document
>   - select a thing, copy, paste
>   - close the document (without saving)
>   - press Mark Heap in Instruments
>   - goto (1)
> 
> Ideally, each "Heapshot" iteration should show 0 growth in almost all cases.
> 
> enjoy,
> 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/rols%40rols.org
> 
> This email sent to r...@rols.org

___

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 arch...@mail-archive.com

Re: [Q] Using NSInvocation vs. selector with NSTimer

2010-10-18 Thread JongAm Park

On 10/17/2010 4:11 PM, Joar Wingfors wrote:

On 17 okt 2010, at 15.51, JongAm Park wrote:

Although I know that NSInvocation was added (from Leopard?), I didn't use it
much.

NSInvocation predates Mac OS X...

Oh. right. I forgot that.

Is there any benefit in using it? My guess is that an NSInvocation instance is used
repeatedly, but using the "selector" based method is not inconvenient for the
most of cases.
Is there any other benefit in using the NSInvocation?

NSInvocation is a very flexible class, and can be used for a wide variety of
tasks, but it is also (therefore) more cumbersome to setup and use for the
simpler things that you mention. It is not often used, so if you don't know
that you need it, you probably don't.

j o a r

Well, what I asked actually is about the design philosophy and what the
intention of creating of that was. Your last statement can't fulfill my
curiosity. :)

Thanks anyway to spare your time to answer my question.

--
--
子曰 不而不改 是謂過矣니라
공자께서 말씀하시길, 잘못을 하고도 고치지 않는 것, 그것을 잘못이라 한다.
- 論語< 衛 靈 公>편

JongAm Park
jongamp...@sbcglobal.net
Visit my personal blog at http://jongampark.blogspot.com
Visit my technical blog at http://jongampark.wordpress.com

___

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 arch...@mail-archive.com

68 matches

Mail list logo