view-based nstableview advice

[Rick C.]

Hi,

Just trying to make sure I'm on the right track here...so I'm doing my first 
view-based table view and I do like how I can set a lot of things up in IB like 
text fields, etc.  But I want to customize the rows (give them a gradient, 
etc.) so am I understanding correctly that I should drag out a custom view in 
IB onto my table view and set that to a subclass of NSTableRowView, set its 
identifier to NSTableViewRowViewKey, then do my custom drawing in that 
subclass?  I'm asking because it seems I can do custom drawing in a 
NSTableCellView subclass as well?  Thanks for the pointers,

rc
___

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Crash in NSBitmapImageRep representationUsingType: NSPNGFileType for 8-bit grayscale

[John Horigan]

I have code that produces a PNG file from a cropped version of a bitmap that 
can be 8-bit grayscale, 16-bit grayscale, 24-bit color, or 32-bit color+alpha. 
It basically looks like this:

- (NSData *) getPNGCropped: (NSRect)cropRect
{
unsigned char* planes[5];
int offset =(int)cropRect.origin.y * _bytesPerRow + 
(int)cropRect.origin.x * (_bitsPerPixel >> 3);
for (unsigned int i = 0; i < 5; ++i)
planes[i] = _imagePlanes[i] ? (_imagePlanes[i] + offset) : NULL;
int width = (int)cropRect.size.width;
int height = (int)cropRect.size.height;

NSBitmapImageRep* bits = 
   [[[NSBitmapImageRep alloc]
 initWithBitmapDataPlanes: planes
   pixelsWide: width
   pixelsHigh: height
bitsPerSample: _bitsPerSample
  samplesPerPixel: _samplesPerPixel
 hasAlpha: _hasAlpha
 isPlanar: _isPlanar
   colorSpaceName: _colorSpace
  bytesPerRow: _bytesPerRow
 bitsPerPixel: _bitsPerPixel
 ] autorelease];

return [bits representationUsingType: NSPNGFileType properties: nil];
}

_planes[0] points to the mutableBytes of an NSMutableData and _planes[1 .. 4] 
point to nil

The NSMutableData contains a bitmap that my code is continuously modifying. 
Periodically the code makes an NSBitmapImageRep from this bitmap and displays 
it or creates a PNG file. There is a companion method that creates an uncropped 
NSBitmapImageRep, this method never crashes. 

This cropping method crashes with SIGABRT in the representationUsingType method 
call if the source bitmap is 8-bit grayscale and planes[0] is not aligned on an 
8-byte boundary. For 16-bit grayscale or 24- or 32- bit color there does not 
seem to be any alignment requirement. If the bitmap is 8-bit grayscale and 
planes[0] is on an 8-byte boundary then it works fine.

This seems to be a specific problem with  creating a PNG file. If I take the 
same NSBitmapImageRep and drop it into a NSImage I can draw with it just fine. 
If I change the file type to NSJPEGFileType it does not crash.

-- john

___

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Passing data through a segue

[Rick Mann]

I have a simple storyboard app with a push segue from a master table to a 
detail controller. In the past, I'd implement -didSelectRowAtIndexPath, get the 
object for that row, create the detail view controller, assign the object to 
it, and push it.

Now I don't really see a nice way to do that without an ivar in the master view 
controller. I can either override prepareForSegue, in which case I won't have 
the index path available, or call performSegue, in which case I won't have the 
destination view controller available.

Am I missing something, or must I store the object in an ivar in one, and get 
at it in the other?

TIA,
Rick


___

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Passing data through a segue

[Rick Mann]

Oh. It seems I can't even implement didSelectRowAtIndexPath; it's not getting 
called.

If the docs for didSelectRowAtIndexPath had been updated to talk about it's use 
in the context of segues, I wouldn't have to read every word of every other doc 
published to try to find the answer.

-- 
Rick

On Apr 2, 2012, at 3:57 , Rick Mann wrote:

> I have a simple storyboard app with a push segue from a master table to a 
> detail controller. In the past, I'd implement -didSelectRowAtIndexPath, get 
> the object for that row, create the detail view controller, assign the object 
> to it, and push it.
> 
> Now I don't really see a nice way to do that without an ivar in the master 
> view controller. I can either override prepareForSegue, in which case I won't 
> have the index path available, or call performSegue, in which case I won't 
> have the destination view controller available.
> 
> Am I missing something, or must I store the object in an ivar in one, and get 
> at it in the other?
> 
> TIA,
> Rick
> 
> 
> ___
> 
> 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:
> https://lists.apple.com/mailman/options/cocoa-dev/rmann%40latencyzero.com
> 
> This email sent to rm...@latencyzero.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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Passing data through a segue

[Roland King]

in -didSelectRowAtIndexPath you get the object then you call 
performSegue:withIdentifer:sender with the object you just got as the sender. 

in -prepareForSegue you have the destination view controller from the segue 
object and you have the 'object' you used as sender, the object from your 
table. Set that object into your destination view controller and you are done. 

Sender is a bit of a bad choice for that parameter I think, you can see why 
it's called that because in the case of a normal button type segue it is the 
button you pressed so it's a sender, but if you use performSegue:: yourself you 
can send anything you like and pick it back up in the prepareForSegue method. 

I suppose alternatively you could use the master table as your 'sender', get 
the indexPathForSelectedRow and use the master table's datasource to look that 
up in the prepareForSegue method, but .. why bother, it's so easy the other 
way. 

On Apr 2, 2012, at 6:57 PM, Rick Mann wrote:

> I have a simple storyboard app with a push segue from a master table to a 
> detail controller. In the past, I'd implement -didSelectRowAtIndexPath, get 
> the object for that row, create the detail view controller, assign the object 
> to it, and push it.
> 
> Now I don't really see a nice way to do that without an ivar in the master 
> view controller. I can either override prepareForSegue, in which case I won't 
> have the index path available, or call performSegue, in which case I won't 
> have the destination view controller available.
> 
> Am I missing something, or must I store the object in an ivar in one, and get 
> at it in the other?
> 
> TIA,
> Rick
> 
> 
> ___
> 
> 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:
> https://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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Passing data through a segue

[Rick Mann]

Thanks for the quick response.

I think I'm okay with sending stuff through the sender parameter, although I do 
agree it's a bit ugly.

Problem is, my didSelectRowAtIndexPath isn't getting called... :-( The delegate 
is set correctly, so I'm assuming iOS doesn't call it in the presence of 
segues? It IS calling prepareSegue...

-- 
Rick

On Apr 2, 2012, at 4:10 , Roland King wrote:

> in -didSelectRowAtIndexPath you get the object then you call 
> performSegue:withIdentifer:sender with the object you just got as the sender. 
> 
> in -prepareForSegue you have the destination view controller from the segue 
> object and you have the 'object' you used as sender, the object from your 
> table. Set that object into your destination view controller and you are 
> done. 
> 
> Sender is a bit of a bad choice for that parameter I think, you can see why 
> it's called that because in the case of a normal button type segue it is the 
> button you pressed so it's a sender, but if you use performSegue:: yourself 
> you can send anything you like and pick it back up in the prepareForSegue 
> method. 
> 
> I suppose alternatively you could use the master table as your 'sender', get 
> the indexPathForSelectedRow and use the master table's datasource to look 
> that up in the prepareForSegue method, but .. why bother, it's so easy the 
> other way. 
> 
> On Apr 2, 2012, at 6:57 PM, Rick Mann wrote:
> 
>> I have a simple storyboard app with a push segue from a master table to a 
>> detail controller. In the past, I'd implement -didSelectRowAtIndexPath, get 
>> the object for that row, create the detail view controller, assign the 
>> object to it, and push it.
>> 
>> Now I don't really see a nice way to do that without an ivar in the master 
>> view controller. I can either override prepareForSegue, in which case I 
>> won't have the index path available, or call performSegue, in which case I 
>> won't have the destination view controller available.
>> 
>> Am I missing something, or must I store the object in an ivar in one, and 
>> get at it in the other?
>> 
>> TIA,
>> Rick
>> 
>> 
>> ___
>> 
>> 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:
>> https://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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Passing data through a segue

[Rick Mann]

Ah, finally found some docs. In the View Controller Programming Guide, 
"Configuring the Destination Controller When a Segue is Triggered", it uses 
-indexPathForSelectedRow.


On Apr 2, 2012, at 4:15 , Rick Mann wrote:

> Thanks for the quick response.
> 
> I think I'm okay with sending stuff through the sender parameter, although I 
> do agree it's a bit ugly.
> 
> Problem is, my didSelectRowAtIndexPath isn't getting called... :-( The 
> delegate is set correctly, so I'm assuming iOS doesn't call it in the 
> presence of segues? It IS calling prepareSegue...
> 
> -- 
> Rick
> 
> On Apr 2, 2012, at 4:10 , Roland King wrote:
> 
>> in -didSelectRowAtIndexPath you get the object then you call 
>> performSegue:withIdentifer:sender with the object you just got as the 
>> sender. 
>> 
>> in -prepareForSegue you have the destination view controller from the segue 
>> object and you have the 'object' you used as sender, the object from your 
>> table. Set that object into your destination view controller and you are 
>> done. 
>> 
>> Sender is a bit of a bad choice for that parameter I think, you can see why 
>> it's called that because in the case of a normal button type segue it is the 
>> button you pressed so it's a sender, but if you use performSegue:: yourself 
>> you can send anything you like and pick it back up in the prepareForSegue 
>> method. 
>> 
>> I suppose alternatively you could use the master table as your 'sender', get 
>> the indexPathForSelectedRow and use the master table's datasource to look 
>> that up in the prepareForSegue method, but .. why bother, it's so easy the 
>> other way. 
>> 
>> On Apr 2, 2012, at 6:57 PM, Rick Mann wrote:
>> 
>>> I have a simple storyboard app with a push segue from a master table to a 
>>> detail controller. In the past, I'd implement -didSelectRowAtIndexPath, get 
>>> the object for that row, create the detail view controller, assign the 
>>> object to it, and push it.
>>> 
>>> Now I don't really see a nice way to do that without an ivar in the master 
>>> view controller. I can either override prepareForSegue, in which case I 
>>> won't have the index path available, or call performSegue, in which case I 
>>> won't have the destination view controller available.
>>> 
>>> Am I missing something, or must I store the object in an ivar in one, and 
>>> get at it in the other?
>>> 
>>> TIA,
>>> Rick
>>> 
>>> 
>>> ___
>>> 
>>> 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:
>>> https://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:
> https://lists.apple.com/mailman/options/cocoa-dev/rmann%40latencyzero.com
> 
> This email sent to rm...@latencyzero.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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Passing data through a segue

[Roland King]

What's your trigger for the segue? Have you set it up in IB so that a select on 
the table cell triggers it automagically? 

If so then no you have probably lost control of didSelect...

So you have two choices. Either do the second thing I said, find the sending 
tableViewController, get its selected index path in the prepareForSegue: call 
and then get your object there, or don't bind the segue direct to the 
tableview, just make a segue (named) between the two view controllers. Nothing 
will trigger that, only segues starting from user interface elements like 
buttons trigger theselves. (to do this I usually drag from the UIVC yellow box 
icon to the second VC). You should then get your didSelect,... call and you can 
call the performSegue: yourself. 

There's probably about another 4 ways to skin that particular cat, I've found 
storyboards and segues to be quite flexible, so flexible sometimes they just 
fall off! 



On Apr 2, 2012, at 7:15 PM, Rick Mann wrote:

> Thanks for the quick response.
> 
> I think I'm okay with sending stuff through the sender parameter, although I 
> do agree it's a bit ugly.
> 
> Problem is, my didSelectRowAtIndexPath isn't getting called... :-( The 
> delegate is set correctly, so I'm assuming iOS doesn't call it in the 
> presence of segues? It IS calling prepareSegue...
> 
> -- 
> Rick
> 
> On Apr 2, 2012, at 4:10 , Roland King wrote:
> 
>> in -didSelectRowAtIndexPath you get the object then you call 
>> performSegue:withIdentifer:sender with the object you just got as the 
>> sender. 
>> 
>> in -prepareForSegue you have the destination view controller from the segue 
>> object and you have the 'object' you used as sender, the object from your 
>> table. Set that object into your destination view controller and you are 
>> done. 
>> 
>> Sender is a bit of a bad choice for that parameter I think, you can see why 
>> it's called that because in the case of a normal button type segue it is the 
>> button you pressed so it's a sender, but if you use performSegue:: yourself 
>> you can send anything you like and pick it back up in the prepareForSegue 
>> method. 
>> 
>> I suppose alternatively you could use the master table as your 'sender', get 
>> the indexPathForSelectedRow and use the master table's datasource to look 
>> that up in the prepareForSegue method, but .. why bother, it's so easy the 
>> other way. 
>> 
>> On Apr 2, 2012, at 6:57 PM, Rick Mann wrote:
>> 
>>> I have a simple storyboard app with a push segue from a master table to a 
>>> detail controller. In the past, I'd implement -didSelectRowAtIndexPath, get 
>>> the object for that row, create the detail view controller, assign the 
>>> object to it, and push it.
>>> 
>>> Now I don't really see a nice way to do that without an ivar in the master 
>>> view controller. I can either override prepareForSegue, in which case I 
>>> won't have the index path available, or call performSegue, in which case I 
>>> won't have the destination view controller available.
>>> 
>>> Am I missing something, or must I store the object in an ivar in one, and 
>>> get at it in the other?
>>> 
>>> TIA,
>>> Rick
>>> 
>>> 
>>> ___
>>> 
>>> 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:
>>> https://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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Passing data through a segue

[Marco Tabini]

On 2012-04-02, at 7:15 AM, Rick Mann wrote:

> Thanks for the quick response.
> 
> I think I'm okay with sending stuff through the sender parameter, although I 
> do agree it's a bit ugly.
> 
> Problem is, my didSelectRowAtIndexPath isn't getting called... :-( The 
> delegate is set correctly, so I'm assuming iOS doesn't call it in the 
> presence of segues? It IS calling prepareSegue...

Have you tried to override -prepareForSegue:sender: and use -[UITableView 
indexPathForSelectedRow] to retrieve the selected row? That does the trick for 
me.

Incidentally, you'll probably find that -willSelectRowAtIndexPath does get 
called.

Cheers,


—Mt.
___

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Passing data through a segue

[Rick Mann]

On Apr 2, 2012, at 4:23 , Marco Tabini wrote:

> Have you tried to override -prepareForSegue:sender: and use -[UITableView 
> indexPathForSelectedRow] to retrieve the selected row? That does the trick 
> for me.

Thanks, that's how I ended up doing it.


___

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Passing data through a segue

[Rick Mann]

On Apr 2, 2012, at 4:23 , Roland King wrote:

> Either do the second thing I said


Yup, that's what I ended up doing. Thanks for pointing out the segue trigger; I 
didn't know how/where to adjust that.

-- 
Rick


___

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Changed cell identifier, now it's not found?

[Rick Mann]

Huh. I changed the name of one of my prototype cells in the storyboard file, 
and changed it in the code, and now iOS can't find it. I've copied-and-pasted 
the name used in the string I pass into the IB field just to be sure there 
wasn't a typo, but I get an exception when I try to dequeue it. Any ideas?

Thanks,
Rick


___

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Changed cell identifier, now it's not found?

[Rick Mann]

Ugh, nvm, I can't read. The class I added didn't get added to the target, and 
it was complaining about the class missing.

Seems like Xc4 always forgets to add new files to the target.



Huh. I changed the name of one of my prototype cells in the storyboard file, 
and changed it in the code, and now iOS can't find it. I've copied-and-pasted 
the name used in the string I pass into the IB field just to be sure there 
wasn't a typo, but I get an exception when I try to dequeue it. Any ideas?

Thanks,
Rick


___

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Changed cell identifier, now it's not found?

[Eric E Dolecki]

Clean the project?

Sent from my Jedi mind.

On Apr 2, 2012, at 7:35 AM, Rick Mann  wrote:

> Huh. I changed the name of one of my prototype cells in the storyboard file, 
> and changed it in the code, and now iOS can't find it. I've copied-and-pasted 
> the name used in the string I pass into the IB field just to be sure there 
> wasn't a typo, but I get an exception when I try to dequeue it. Any ideas?
> 
> Thanks,
> Rick
> 
> 
> ___
> 
> 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:
> https://lists.apple.com/mailman/options/cocoa-dev/edolecki%40gmail.com
> 
> This email sent to edole...@gmail.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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Stenography

[Reaves, Timothy]

He wants to write an app that will take a picture of shorthand and turn it
in to text.


On Sun, Apr 1, 2012 at 7:07 AM, Gregory Weston  wrote:

> deoxy t2 wrote:
>
> > I'm new to the list and new in Objective-C and Apple programming and I
> have a very timely question, I want to manipulate images to develop
> stenography, but do not know where begin. I'm reading:1.-vImage Programming
> Guide2 Core Image Programming Guide
> > But it is not clear which library is correct in order to manipulate
> images and achieve what I want.
> > any ideas?.
>
> Just so we're clear, you're asking about steGAnography, right?
>
> ___
>
> 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:
>
> https://lists.apple.com/mailman/options/cocoa-dev/treaves%40silverfieldstech.com
>
> This email sent to trea...@silverfieldstech.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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

RE: Stenography

[Kirk Kerekes]

For the sake of later Googlers, the word is "Steganography" 
(. 

"Stenography" is writing in shorthand.

NSBitMapImageRep allows individual pixel access.

On Apr 1, 2012, at 12:16 AM, cocoa-dev-requ...@lists.apple.com wrote:

> Message: 9
> Date: Tue, 27 Mar 2012 20:19:26 +
> From: deoxy t2 
> To: cocoa-dev@lists.apple.com
> Subject: Stenography
> Message-ID: 
> Content-Type: text/plain; charset="iso-8859-1"
> 
> 
> 
> Hello friends.
> I'm new to the list and new in Objective-C and Apple programming and I have a 
> very timely question, I want to manipulate images to develop stenography, but 
> do not know where begin. I'm reading:1.-vImage Programming Guide2 Core Image 
> Programming Guide
> But it is not clear which library is correct in order to manipulate images 
> and achieve what I want.
> any ideas?.
> Thanks a lot.
> deoxyt2.-
> http://deoxyt2.livejournal.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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Stenography

[vincent habchi]

Le 2 avr. 2012 à 14:37, "Reaves, Timothy"  a 
écrit :

> He wants to write an app that will take a picture of shorthand and turn it
> in to text.

Stenography (Greek stenos-: reduced) is an obsolete system of script 
secretaries used to take notes on the fly. I’m not sure, but I think it is a 
syllabic script. I don’t think anybody use it anymore: it has been superseded 
by Siri :)
> 

Steganography comes from Greek steganos, roof, wherefore it’s use for 
obfuscated communications.

Vincent


___

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Stenography

[Alex Zavatone]

Thank you Kirk.  

It pays to actually be able to spell the term you are asking people for advice 
on.


On Apr 2, 2012, at 8:42 AM, Kirk Kerekes wrote:

> For the sake of later Googlers, the word is "Steganography" 
> (. 
> 
> "Stenography" is writing in shorthand.
> 
> NSBitMapImageRep allows individual pixel access.
> 
> On Apr 1, 2012, at 12:16 AM, cocoa-dev-requ...@lists.apple.com wrote:

___

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Stenography

[Mikkel Islay]

This may be a case of selective perception.  Apparently Cocoa-developer are 
more familiar with steganography than shorthand.  :) 
Since the original poster explicitly wrote "stenography", it seems plausible 
that was what he meant.

In fact, i know that trainee journalists in the UK are taught shorthand, even 
though it seems surprising. No doubt the same applies for other countries (and 
professions) as well. For all their virtues smart-phones and tablets have some 
limitations when it comes to text-input. An app for transcribing shorthand to 
longhand would have its uses and audience, no doubt.

Mikkel


On 2 Apr 2012, at 14:49, Alex Zavatone wrote:

> Thank you Kirk.  
> 
> It pays to actually be able to spell the term you are asking people for 
> advice on.
> 
> 
> On Apr 2, 2012, at 8:42 AM, Kirk Kerekes wrote:
> 
>> For the sake of later Googlers, the word is "Steganography" 
>> (. 
>> 
>> "Stenography" is writing in shorthand.
>> 
>> NSBitMapImageRep allows individual pixel access.
>> 
>> On Apr 1, 2012, at 12:16 AM, cocoa-dev-requ...@lists.apple.com wrote:
> 
> ___
> 
> 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:
> https://lists.apple.com/mailman/options/cocoa-dev/my.inputstream%40googlemail.com
> 
> This email sent to my.inputstr...@googlemail.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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Stenography

[Peter Teeson]

On 2012-04-02, at 8:46 AM, vincent habchi wrote:
> Le 2 avr. 2012 à 14:37, "Reaves, Timothy"  a 
> écrit :
>> He wants to write an app that will take a picture of shorthand and turn it 
>> into text.
> Stenography (Greek stenos-: reduced) is an obsolete system of script 
> secretaries used to take notes on the fly.
> I’m not sure, but I think it is a syllabic script. I don’t think anybody uses 
> it anymore: it has been superseded by Siri :)
Indeed. I had a secretary who knew both Pitman and Gregg stenography methods. 
That dates me for sure.
(She would then go to a typewriter to produce the letter or article - hehehehe)
Perhaps a current use of a similar mechanism would be a court reporter or the 
Congressional floor reporters 
walking around to each person speaking.
> Steganography comes from Greek steganos, roof, wherefore it’s use for 
> obfuscated communications.
Fascinating article.. thanks.
___

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: drawRect using a Category

[Peter Teeson]

Thank you all for your patience and kindness in educating me.
I appreciate it very much. I will sub-class which is what I have previously 
done.
This was, for me, a bit of an experiment (which failed). But that's also a good 
result.

Thanks again.

Peter
On 2012-04-02, at 12:44 AM, Jens Alfke wrote:
> On Mar 31, 2012, at 6:46 PM, Peter Teeson wrote:
>> In my app there is only the one NSMatrix instance 
> 
> There's no way to tell, really. For all I know, the Open or Save panels might 
> use NSMatrix.
> Or the Find panel or the font panel. Heck, I believe in the old days of 
> OpenStep,
> menus were implemented as NSMatrixes of menu item cells.
> 
> Also, if you ever need to add another different NSMatrix somewhere else in 
> your app,
> you're now SOL because you'll now have to rip out the category method and 
> re-implement
> your code the right way using subclassing.
> 
>> Although I do [super drawRect] after my own drawing.
> 
> That won't call the old NSMatrix drawRect, it'll call the drawRect of the 
> superclass of NSMatrix,
> which is NSControl. You've effectively deleted the original NSMatrix drawRect 
> implementation,
> so it's impossible to call it without some tricky gymnastics. One more time: 
> a category doesn't override
> a method, it replaces it. It literally edits the class's method table to 
> replace the old function pointer with the new one.
> The only way to properly override a method, in the OOP sense, is to make a 
> subclass.
> 
> —Jens

___

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Stenography

[Lee Ann Rucker]

On Apr 2, 2012, at 8:18 AM, Peter Teeson wrote:

> On 2012-04-02, at 8:46 AM, vincent habchi wrote:
>> Le 2 avr. 2012 à 14:37, "Reaves, Timothy"  a 
>> écrit :
>>> He wants to write an app that will take a picture of shorthand and turn it 
>>> into text.
>> Stenography (Greek stenos-: reduced) is an obsolete system of script 
>> secretaries used to take notes on the fly.
>> I’m not sure, but I think it is a syllabic script. I don’t think anybody 
>> uses it anymore: it has been superseded by Siri :)
> Indeed. I had a secretary who knew both Pitman and Gregg stenography methods. 
> That dates me for sure.
> (She would then go to a typewriter to produce the letter or article - 
> hehehehe)
> Perhaps a current use of a similar mechanism would be a court reporter or the 
> Congressional floor reporters 
> walking around to each person speaking.
>> Steganography comes from Greek steganos, roof, wherefore it’s use for 
>> obfuscated communications.
> Fascinating article.. thanks.

Well, there is some crossover - some stenographers had a style so idiosyncratic 
that only they could read it.


___

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Stenography

[Peter Teeson]

On 2012-04-02, at 2:24 PM, Lee Ann Rucker wrote:

> 
> On Apr 2, 2012, at 8:18 AM, Peter Teeson wrote:
> 
>> On 2012-04-02, at 8:46 AM, vincent habchi wrote:
>>> Le 2 avr. 2012 à 14:37, "Reaves, Timothy"  a 
>>> écrit :
 He wants to write an app that will take a picture of shorthand and turn it 
 into text.
>>> Stenography (Greek stenos-: reduced) is an obsolete system of script 
>>> secretaries used to take notes on the fly.
>>> I’m not sure, but I think it is a syllabic script. I don’t think anybody 
>>> uses it anymore: it has been superseded by Siri :)
>> Indeed. I had a secretary who knew both Pitman and Gregg stenography 
>> methods. That dates me for sure.
>> (She would then go to a typewriter to produce the letter or article - 
>> hehehehe)
>> Perhaps a current use of a similar mechanism would be a court reporter or 
>> the Congressional floor reporters 
>> walking around to each person speaking.
>>> Steganography comes from Greek steganos, roof, wherefore it’s use for 
>>> obfuscated communications.
>> Fascinating article.. thanks.
> Well, there is some crossover - some stenographers had a style so 
> idiosyncratic that only they could read it.
ROTFL


___

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: view-based nstableview advice

[Uli Kusterer]

On 02.04.2012, at 08:58, Rick C. wrote:
> Just trying to make sure I'm on the right track here...so I'm doing my first 
> view-based table view and I do like how I can set a lot of things up in IB 
> like text fields, etc.  But I want to customize the rows (give them a 
> gradient, etc.) so am I understanding correctly that I should drag out a 
> custom view in IB onto my table view and set that to a subclass of 
> NSTableRowView, set its identifier to NSTableViewRowViewKey, then do my 
> custom drawing in that subclass?  I'm asking because it seems I can do custom 
> drawing in a NSTableCellView subclass as well?  Thanks for the pointers,


 If I understand you correctly, you're mixing things up. The identifier is the 
reuse identifier. I.e. all cells with the same identifier are considered 
interchangeable when the table needs a new cell, so if there's an unused cell 
with the same identifier, it will be used.

 Setting the identifier has no effect on the kind of cell class that is 
created. The cell class is determined by the "Custom Class" of the view in the 
XIB file, not by its identifier.

 You could theoretically use the same class for all your cells, but use 
different constructors to set up their internals differently based on different 
reuse identifiers. That's why the identifier is separate from the cell class.

Cheers,
-- Uli Kusterer
"The Witnesses of TeachText are everywhere..."
http://www.lookandfeelcast.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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

NSObject hierarchy browser. Is there such a thing?

[Alex Zavatone]

I come from the ancient, forgotten world of Director, where I was fortunate 
enough to write an object method and object hierarchy browser that showed the 
variable type :  variable value or the methods in the object hierarchy.

This made programming painfully easy for me since I had a readout that brought 
all the watched objects into scope and displayed their variable structure and 
another one that displayed all the inherited methods.

With all the information to access about all the NS and iOS frameworks, I am 
wondering if there is something like this for the main classes in the iOS UIKit 
and Foundation frameworks?

The "dwell over a variable" tooltip has its purpose, but leaves much to be 
desired.

Even hierarchical printouts of the method and variable structure would rock in 
illustrating all the vars/methods I have to look up every day.

Everything's just not exactly second nature to me yet and these training wheels 
will certainly help me get less skinned knees and save a boatload of time.

Many thanks.
- Alex Zavatone
___

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: NSObject hierarchy browser. Is there such a thing?

[jonat...@mugginsoft.com]

On 2 Apr 2012, at 21:56, Alex Zavatone wrote:

> I come from the ancient, forgotten world of Director, where I was fortunate 
> enough to write an object method and object hierarchy browser that showed the 
> variable type :  variable value or the methods in the object hierarchy.
> 
> This made programming painfully easy for me since I had a readout that 
> brought all the watched objects into scope and displayed their variable 
> structure and another one that displayed all the inherited methods.
> 
> With all the information to access about all the NS and iOS frameworks, I am 
> wondering if there is something like this for the main classes in the iOS 
> UIKit and Foundation frameworks?
> 
> The "dwell over a variable" tooltip has its purpose, but leaves much to be 
> desired.
> 
> Even hierarchical printouts of the method and variable structure would rock 
> in illustrating all the vars/methods I have to look up every day.
> 
> Everything's just not exactly second nature to me yet and these training 
> wheels will certainly help me get less skinned knees and save a boatload of 
> time.
I am not sure about iOS coverage but I have used the following for OS X:

http://homepage.mac.com/aglee/downloads/appkido.html
www.fscript.org
http://inexdo.com/CocoaNav

Regards

Jonathan Mitchell
Mugginsoft LLP
___

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: NSObject hierarchy browser. Is there such a thing?

[Tito Ciuro]

Hello,

FYI… CocoaNav doesn't seem to be working on Mac OS X Lion 10.7.3 (crashes in 
RBApplicationMain)

-- Tito

On Apr 2, 2012, at 6:04 PM, jonat...@mugginsoft.com wrote:

> http://inexdo.com/CocoaNav

___

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Calendar heatmap-ness ala iCal

[Jeremy Matthews]

So for one of my apps I'd like to create a ical-like heatmap (if you switch to 
the year view in iCal it shows daily activity via color-coding) based on some 
internal data...I was wondering if there were any ideas on how to get a view 
like that without having to reinvent the wheel...any ideas?

Thanks,
jeremy
___

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: NSObject hierarchy browser. Is there such a thing?

[Alex Zavatone]

These apps are working (awesomely, I might add) on 10.6.8

AppKiDo and AppKiDo-for-iPhone
F-Script


CocoaNav launches and hangs after launch.

Thank you.  AppKiDo looks awesome.  



On Apr 2, 2012, at 5:16 PM, Tito Ciuro wrote:

> Hello,
> 
> FYI… CocoaNav doesn't seem to be working on Mac OS X Lion 10.7.3 (crashes in 
> RBApplicationMain)
> 
> -- Tito
> 
> On Apr 2, 2012, at 6:04 PM, jonat...@mugginsoft.com wrote:
> 
>> http://inexdo.com/CocoaNav
> 
> ___
> 
> 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:
> https://lists.apple.com/mailman/options/cocoa-dev/zav%40mac.com
> 
> This email sent to z...@mac.com

- Alex Zavatone




___

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Core Data Automatic Lightweight Migration

[Richard Somers]

On Apr 2, 2012, at 4:20 PM, Richard Somers wrote:

> Can anyone shed some light on this?

It appears that others have also recently experienced frustration with 
automatic lightweight migration and have come up with zero answers.

Jan 26, 2012

http://stackoverflow.com/questions/9014668/core-data-automatic-lightweight-migration-failing-in-xcode-4-using-process-the-w

Mar 20, 2012

http://stackoverflow.com/questions/9791706/automatic-core-data-migration-fails-on-mac-os-x-10-5-but-not-on-10-6-or-10-7

--Richard


___

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: NSDocument disc undo stack

[Steven]

If there's no mechanism to persist the app undo states and undo manager 
messages, how should apps that support undo work with the automatic termination 
behaviour ?
Should automatic termination be set dynamically and disabled when undo history 
is present ?
A user might be annoyed if the undo history were lost when the app went off 
screen.

"the system may also quit an app with open windows if the app is not currently 
on screen, perhaps because the user hid it or switched spaces."

TextEdit (in 10.7) retains its undo history beyond save, until the document or 
application is closed.

Steven.


> 
> 
> On 25/03/2012, at 5:34 AM, Doug Clinton wrote:
> 
>> I don't know if this was the issue that Steven was asking about, but I've 
>> been wondering if there is a recommended way to persist the undo stack so 
>> that it's still available if you restart the app, or close and re-open the 
>> document. It's always bothered me that there is this great mechanism for 
>> handling undo, but that all the history is thrown away when you close the 
>> app.
> 
> 
> No easy way I know of. The undo architecture relies on a huge amount of state 
> within the app external to the undo stack itself. You'd have to save all of 
> that state somehow.
> 
> In fact, most apps throw away the undo history on a document save (you 
> arrange this), as a way to recover the memory used by undo, since the whole 
> state is being saved in the file anyway. Versions are the supported mechanism 
> for persistent document undo.
> 
> --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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: view-based nstableview advice

[Rick C.]

It's definitely possible I'm mixing things up. :-)

So to create a subclass to further customize the look of my cells beyond the 
basics I should be subclassing NSTableRowView correct?  From what I've seen in 
the documentation Apple is just dragging a new view onto the table view and 
setting that view to their subclass right?  Since there's no actual 
NSTableRowView object in IB.  But if I don't set its User Interface Item 
Identifier to NSTableViewRowViewKey the table view will not draw with my 
subclass.  Ok I suppose I could write it in code but I was trying to do it as 
code-free as possible.  Thanks for the help,

rc



On Apr 3, 2012, at 3:24 AM, Uli Kusterer wrote:

> On 02.04.2012, at 08:58, Rick C. wrote:
>> Just trying to make sure I'm on the right track here...so I'm doing my first 
>> view-based table view and I do like how I can set a lot of things up in IB 
>> like text fields, etc.  But I want to customize the rows (give them a 
>> gradient, etc.) so am I understanding correctly that I should drag out a 
>> custom view in IB onto my table view and set that to a subclass of 
>> NSTableRowView, set its identifier to NSTableViewRowViewKey, then do my 
>> custom drawing in that subclass?  I'm asking because it seems I can do 
>> custom drawing in a NSTableCellView subclass as well?  Thanks for the 
>> pointers,
> 
> 
> If I understand you correctly, you're mixing things up. The identifier is the 
> reuse identifier. I.e. all cells with the same identifier are considered 
> interchangeable when the table needs a new cell, so if there's an unused cell 
> with the same identifier, it will be used.
> 
> Setting the identifier has no effect on the kind of cell class that is 
> created. The cell class is determined by the "Custom Class" of the view in 
> the XIB file, not by its identifier.
> 
> You could theoretically use the same class for all your cells, but use 
> different constructors to set up their internals differently based on 
> different reuse identifiers. That's why the identifier is separate from the 
> cell class.
> 
> Cheers,
> -- Uli Kusterer
> "The Witnesses of TeachText are everywhere..."
> http://www.lookandfeelcast.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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Can't get UTI to stick

[Jo Meder]

Hi,

I've written a Quick Look generator for one of my app's file types. As part of 
that I've defined a UTI for that file type. However whatever I do I can't the 
UTI to stick. I've rebuilt the app, moved it around and used lsregister to kill 
the Launch Services database and rebuild it. Dumping the Launch Services 
database shows that the UTI isn't being picked up from the app. It's not 
happening on 10.5 or 10.6. Here are the relevant parts of my app's plist:

UTExportedTypeDeclarations


UTTypeTagSpecification

public.filename-extension

tgc
TGC


UTTypeDescription
Terragen 2 Clip document
UTTypeConformsTo

public.xml

UTTypeIdentifier


uk.co.planetside.Terragen_2.clip




CFBundleDocumentTypes


LSItemContentTypes


uk.co.planetside.Terragen_2.clip

CFBundleOSTypes

TG2C

CFBundleTypeExtensions

TGC
tgc

CFBundleTypeIconFile
TGC.icns
CFBundleTypeName
Terragen 2 Clip document
CFBundleTypeRole
Editor



I have tried commenting out the CFBundleDocumentTypes section so there is just 
the UTI but that didn't help.

Can you see something wrong with the above? I'd greatly appreciate any help. So 
far I've spent longer trying to get this to work than I did on the Quick Look 
generator itself.

Regards,

Jo Meder
___

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Re: Core Data Automatic Lightweight Migration

[Jerry Krinock]

On 2012 Apr 02, at 15:20, Richard Somers wrote:

> When opening a sqlite document, the document opens without error but a 
> another document "mydocument~.myappsqlite" is created in the same directory 
> as the original.

That is expected behavior.  The "tildefied" document, as I call it (tilde = 
"~") is in fact the old document, prior to migration, which Core Data has 
renamed.  It is an undocumented "feature" of Core Data.  Apparently, the idea 
is that, with help from your Support Department, a distressed user can revert 
if the migration gave undesired results.

So it looks like your SQLite migration is working correctly.  Only your XML 
migration is failing.


___

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com