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 th
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 displayin
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..."
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
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 a
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/
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 w
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
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
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
> So if the master dictionary and the array for the NSTable are
> encapsulated together in a class, you could use NSMutableArray as the
> primary structure, and encapsulate a hidden NSMutableDictionary used
> only for faster searching. Both are maintained in parallel by the
> enclosing class, so
On Oct 18, 2010, at 3:20 AM, Uli Kusterer wrote:
> -> 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
Hi,
I have a server and a client processes running on the same machine.
Per client request, the server does some job and returns the result to
the client in form of some MyObject.
This is the interface vended by the server:
- (out bycopy MyObject*)doSomeJob;
Despite bycopy, I see in debugger th
On Oct 18, 2010, at 10:22 AM, Trygve Inda wrote:
>> So if the master dictionary and the array for the NSTable are
>> encapsulated together in a class, you could use NSMutableArray as the
>> primary structure, and encapsulate a hidden NSMutableDictionary used
>> only for faster searching. Both are
> On Oct 18, 2010, at 10:22 AM, Trygve Inda wrote:
>
>>> So if the master dictionary and the array for the NSTable are
>>> encapsulated together in a class, you could use NSMutableArray as the
>>> primary structure, and encapsulate a hidden NSMutableDictionary used
>>> only for faster searching.
>> On Oct 18, 2010, at 10:22 AM, Trygve Inda wrote:
>>
So if the master dictionary and the array for the NSTable are
encapsulated together in a class, you could use NSMutableArray as the
primary structure, and encapsulate a hidden NSMutableDictionary used
only for faster search
On Oct 18, 2010, at 9:00 AM, JongAm Park wrote:
>>> 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?
>
On Oct 18, 2010, at 8:42 AM, Matt Gough wrote:
> Perhaps Apple should aim Instruments at itself. Inspired by Bill's post, I
> just did a HeapShot test on my own app. Instruments went up to 2.5GB real Mem
> and stayed at that when I closed the Instrument window.
"2.5GB Real Mem" is relatively m
On 10/18/2010 9:45 AM, Keary Suska wrote:
On Oct 18, 2010, at 9:00 AM, JongAm Park wrote:
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 benefi
I'm fairly certain my problem here is that I wasn't thinking about unicode
terms here.
What we are trying to do:
Shorten the AM/PM to just the first character in Western Languages so that a
time is shown as "1:30a".
NSDateFormatter* formatter = [[NSDateFormatter alloc] init];
Hi all,
The block code set by the NSOperation setCompletionBlock: should be executed
automatically
or manually after the NSOperation object finished its task?
I thought it should be automatically and my block code is not executed.
Thanks.
--
==
Life isn't about finding yo
Trygve Inda wrote:
Or does NSArrayController somehow bind to a non-array property,
but one
that responds as if it were an array?
Later in my original post, I suggested subclassing NSMutableArray, so
it can bind to NSArrayController. Your new class, i.e. MyDataClass,
doesn't just respo
On Oct 18, 2010, at 10:59 AM, Trygve Inda wrote:
> I guess I am just not seeing how my NSArrayController would ties to this. So
> I have a class MyDataClass and since my NSTableView is tied to an
> NSArrayController, then the NSArrayController needs to get it's data from
> MyDataClass.
>
> So is
On Oct 18, 2010, at 12:19 PM, Alex Kac wrote:
> I'm fairly certain my problem here is that I wasn't thinking about unicode
> terms here.
>
> What we are trying to do:
> Shorten the AM/PM to just the first character in Western Languages so that a
> time is shown as "1:30a".
>
> NSDateF
> On Oct 18, 2010, at 10:59 AM, Trygve Inda wrote:
>
>> I guess I am just not seeing how my NSArrayController would ties to this. So
>> I have a class MyDataClass and since my NSTableView is tied to an
>> NSArrayController, then the NSArrayController needs to get it's data from
>> MyDataClass.
>>
On Oct 18, 2010, at 2:41 PM, glenn andreas wrote:
>
> On Oct 18, 2010, at 12:19 PM, Alex Kac wrote:
>
>> I'm fairly certain my problem here is that I wasn't thinking about unicode
>> terms here.
>>
>> What we are trying to do:
>> Shorten the AM/PM to just the first character in Western Langu
On Oct 18, 2010, at 10:19, Alex Kac wrote:
> What we are trying to do:
> Shorten the AM/PM to just the first character in Western Languages so that a
> time is shown as "1:30a".
>
> NSDateFormatter* formatter = [[NSDateFormatter alloc] init];
> NSString* am = [[[formatter AMSymbol]
Yes, we already take care of the 24 hour situation. This is explicitly for
people who are showing their times using AM/PM. Not that its an iron-clad thing
either, but we've been doing calendaring for over 10 years now so I'm aware of
the date/time notation by country. But again this is explicitl
Right - some don't. We do take care of those situations. But many do and its
nice to get that from OS itself.
On Oct 18, 2010, at 1:48 PM, A.M. wrote:
>
> On Oct 18, 2010, at 2:41 PM, glenn andreas wrote:
>
>>
>> On Oct 18, 2010, at 12:19 PM, Alex Kac wrote:
>>
>>> I'm fairly certain my prob
Right, our goal is not to make this a universal solution. Just one for the
languages we know and support. Thanks. Appreciate the help.
On Oct 18, 2010, at 1:47 PM, Quincey Morris wrote:
> It's not obvious that taking the first grapheme is going to be semantically
> meaningful in every language
On Oct 18, 2010, at 04:37, Amy Heavey wrote:
> 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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/18/10 10:19 AM, Alex Kac wrote:
> This works in Western languages just fine. However in languages like
> Korean it does not work giving a random character seemingly. From
> reading on this list over time I believe its because I'm just getting
> o
On Oct 18, 2010, at 04:43, Trygve Inda wrote:
> 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
I actually attended that session - so thanks for reminding me about it. I
should add I have worked with unicode, asian languages, etc.. on other
platforms for many years and am aware of the complexities (though I've been
working on the Mac since 1992 and Cocoa since 2007). Its not so much
eye-o
Hi Throsten,
what you suggested is a standard routine, but it reads just flattened image as
it was stored by Photoshop
to a .psd file.
I need to read layer images that are stored in .psd file.
The only way I know is using
>> GraphicsImportSetImageIndex(importer, i);
Where i is an index of im
> On Oct 18, 2010, at 04:43, Trygve Inda wrote:
>
>> 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 be
On 18.10.2010, at 20:49, Alex Kac wrote:
> Yes, we already take care of the 24 hour situation. This is explicitly for
> people who are showing their times using AM/PM. Not that its an iron-clad
> thing either, but we've been doing calendaring for over 10 years now so I'm
> aware of the date/time
Hi,
I'm new to Cocoa. I'm developing a simple application that contains two
TableViews. What I can't figure out is how to distinguish between the two
TableView pointers that are passed in to:
- (int)numberOfRowsInTableView:(NSTableView *) tableView
- (id)tableView:(NSTableView *)tableView
obje
Hi everyone,
I have an NSOutlineView that is backed by a NSTreeController, which is bound
to a Core Data entity. One column in the outlineView is for the entity's
displayName, and the other column is an NSButtonCell. There is an
NSButtonCell for every row in the outlineView.
When a certain row's
On Oct 17, 2010, at 5:29 PM, Chris Share wrote:
> I'm new to Cocoa. I'm developing a simple application that contains two
> TableViews. What I can't figure out is how to distinguish between the two
> TableView pointers that are passed in to:
>
> - (int)numberOfRowsInTableView:(NSTableView *) t
On Oct 17, 2010, at 4:29 PM, Chris Share wrote:
> I'm new to Cocoa. I'm developing a simple application that contains two
> TableViews. What I can't figure out is how to distinguish between the two
> TableView pointers that are passed in to:
>
> - (int)numberOfRowsInTableView:(NSTableView *) t
On 18.10.2010, at 21:08, Alex Kac wrote:
> That all said, everything everyone said is true here about this not being a
> one-size fits all solution. Its not meant to be. That's the one reason I tend
> not to post here much - I feel like sometimes I have to give everyone a full
> design doc along
On 18.10.2010, at 01:29, Chris Share wrote:
> I'm new to Cocoa. I'm developing a simple application that contains two
> TableViews. What I can't figure out is how to distinguish between the two
> TableView pointers that are passed in to:
>
> - (int)numberOfRowsInTableView:(NSTableView *) tableVi
On Oct 18, 2010, at 1:45 PM, Trygve Inda wrote:
> So would you do something like the example you described:
>
> http://homepage.mac.com/mmalc/CocoaExamples/controllers.html
>
> Where the NSArrayController is bound not to an array at all but to a
> property which responds to the proper indexed to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 10/18/10 1:27 PM, Michael Dautermann wrote:
>
> On Oct 17, 2010, at 4:29 PM, Chris Share wrote:
>
>> I'm new to Cocoa. I'm developing a simple application that contains two
>> TableViews. What I can't figure out is how to distinguish between the
Alex,
Uli is giving very helpful recommendations here.
The leave-the-first-character logic doesn't work for Korean and Japanese,
either.
They happen to spell AM/PM like MA/MP as Quincey warned.
If you have specific target locales in mind, I recommend providing a set of
formatting configuratio
> You are mistaking instance variables for properties. Instance variables are
> implementation details, and nothing outside of your class should be aware of
> them.
>
> Properties are part of your interface, essentially the accessor methods and
> their behavior. (Remember that you can have prop
On Oct 18, 2010, at 4:22 PM, Trygve Inda wrote:
> How does it derive the plural for he method name countOfWeapons from the
> class name Weapon?
It doesn’t. The property name is “weapons” in this case, the same name it would
have had if it had been an NSArray. The only difference is that instead
Trygve Inda wrote:
Each dictionary (or object with properties) will need to hold
roughly 9
textual strings, and there will be on the order of 10,000 objects
in the
array. I am guessing that dictionary will perform better than a
predicate
filter given the number of objects.
Never guess a
> On Oct 18, 2010, at 4:22 PM, Trygve Inda wrote:
>
>> How does it derive the plural for he method name countOfWeapons from the
>> class name Weapon?
>
> It doesn’t. The property name is “weapons” in this case, the same name it
> would have had if it had been an NSArray. The only difference is th
> Trygve Inda wrote:
>
>> Each dictionary (or object with properties) will need to hold
>> roughly 9
>> textual strings, and there will be on the order of 10,000 objects
>> in the
>> array. I am guessing that dictionary will perform better than a
>> predicate
>> filter given the number of objects.
On Oct 18, 2010, at 4:42 PM, Trygve Inda wrote:
> So is "weapons" only defined in IB under the Array binding's model key path?
Yep, and Cocoa can automatically generate an array from it for
NSArrayController.
#import
@interface Combatant : NSObject {
@private
id weapon1;
id we
> I’d say the best solution is the one that Ken described. Implement the to-many
> accessors such as countOf, objectInAtIndex:,
> insertObject:inAtIndex:, and so forth. Then the underlying storage
> can be an NSDictionary, a skip list, or whatever you want, and as long as your
> accessors are abst
Trygve Inda wrote:
This is probably true since this is a very minor part of my app...
I simply
need an array to display in a table with the added functionality of
being
able to locate a record uniquely (each object in the array has a
unique ID
as one of it's properties).
I recommend doi
Hi all.
I have a work around for the problem that one runs into with custom subclassed
controls that use custom cells being unarchived from nibs with standard cells.
(this is covered many place, possibly most succinctly here:
http://mikeash.com/pyblog/custom-nscells-done-right.html)
This work
On 19/10/2010, at 7:31 AM, Uli Kusterer wrote:
> This is a code smell, i.e. a sign that you're likely doing something in a way
> that it wasn't intended to be done.
>
> Don't try to distinguish between them, give them each a separate data
> source/delegate object. That way, you get only one ta
On Oct 16, 2010, at 16:23, Jake wrote:
> 2010-10-16 18:06:34.865 Tailr[95389:a0f] Beginng of controller toggle: 1
> 2010-10-16 18:06:34.865 Tailr[95389:a0f] Beginng of model toggle: 1
> 2010-10-16 18:06:34.866 Tailr[95389:a0f] End of model toggle: 0
> 2010-10-16 18:06:34.866 Tailr[95389:a0f] End o
Hello,
I'm about to make a change in the Major version of a framework ( new version
will be B ). I've read through the docs and all but i'm not sure i understand
how to set it up so i keep version A in my build but also build the new version
B.
Has anyone done this and what should i do? Should
On Oct 18, 2010, at 4:50 PM, Alexander Cohen wrote:
> I'm about to make a change in the Major version of a framework ( new version
> will be B ). I've read through the docs and all but i'm not sure i understand
> how to set it up so i keep version A in my build but also build the new
> version
Thanks Nick, this will help a lot, i don't think its explained anywhere in the
docs. You are spot on for why i need to do it. We've got some very old software
that relies on things that have been deprecated for a long time and now we need
to remove them. I think the best option is to rev the maj
Here's one way to accomplish your stated goal:
-- BEGIN CODE --
#import
int main (int argc, const char * argv[]) {
NSAutoreleasePool * pool = [[NSAutoreleasePool alloc] init];
// NSDateFormatter, locale friendly
NSDateFormatter *df = [[NSDateFormatter alloc] init];
[df setDateSt
On Oct 11, 2010, at 2:21 AM, Thorsten Lemke wrote:
> I have a dialog in my app wich should let the user enter a carriage return.
>
> How can I avoid pressing the default button with return? Only enter should
> press it in this case.
As you probably know, implementing this will be hugely popular
On 18 Oct 2010, at 19:56, Bill Bumgarner wrote:
> 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-i
Greetings.
The lead developer at my workplace left his brainchild behind but forgot to
write any documentation for it.
the framework is now quite unusable because it is quite extensive an no one
knows the depth of it's architecture.
I am mandated to document this framework. (Joy!)
The "framewo
On 2010-10-09, at 6:14 AM, Remco Poelstra wrote:
> That seems reasonable, but makes the documentation harder to read. In the old
> days where I used Delphi, the inherited methods were all shown as such and it
> gives a direct overview of what is available. Especially in this case, where
> the
Apparently I was working around a problem that no longer exists for most common
cases. You don't need to do any shenanigans with replacing or overriding
-initWithCoder: to get custom cells to work from IB anymore. To get a custom
cell class unarchived directly from the nib, just keep clicking
On 19 Oct 2010, at 00:54, Alex Kac wrote:
> NSDateFormatter* formatter = [[NSDateFormatter alloc] init];
> NSString* am = [[[formatter AMSymbol] substringToIndex:1]
> lowercaseString];
Please note that substringToIndex does only sometimes return a valid string.
I just tried:
NSS
On Oct 18, 2010, at 20:52, Abhi Beckert wrote:
> [NSObject valueForKey:] has nothing to do with dictionaries. It's an internal
> API feature that's used throughout the framework. The foo.bar syntax is
> essentially an alias for [foo valueForKey:@"bar"]. Understanding exactly how
> this method w
68 matches
Mail list logo
