date:20130123

Re: Best guess at expressing a string as a variable

2013-01-23 Thread jonat...@mugginsoft.com


On 23 Jan 2013, at 01:32, Keary Suska cocoa-...@esoteritech.com wrote:

 On Jan 22, 2013, at 6:18 PM, Jens Alfke wrote:
 
 On Jan 22, 2013, at 3:28 PM, jonat...@mugginsoft.com wrote:
 
 Is  + (id)letterCharacterSet the best choice here?
 
 The API docs say Informally, this set is the set of all characters used as 
 letters of alphabets and ideographs.”
 Which very strongly implies it is not just ASCII, but covers all Unicode 
 alphabets.
 
 Some languages, like Java and Go, can handle non-ASCII letters in 
 identifiers, but most can’t. I would stick with a character set consisting 
 of only upper and lowercase ASCII letters, digits and the underscore. And 
 you’d probably want to force the first character to be a lowercase letter 
 since some languages assign special meaning to identifiers that start with a 
 capital letter or with an underscore.
 
 
 I was thinking that by language the OP meant linguistic rather than 
 programming.
Yes I mean linguistic language rather than programming.

 For the latter it is a bit easier to find the lowest common denominator, 
 which is probably strictly ascii alpha and numbers, beginning with lowercase 
 alpha and probably even a character limit of around 12. That would 
 automatically exclude the identifier pattern example provided as most 
 languages do not permit dashes in identifier names (that I know of).

After a bit more experimenting it is clear that restricting the variable's 
character set is sensible.

I think I will have to introduce an intermediate NSTextView that filters and 
displays the natural language input.
The user can then modify the variable name if necessary before it gets utilised 
further.

So the approach may be:

1. decompose the input with decomposedStringWithCanonicalMapping
2. build a NSMutableCharacterSet that asserts +alphanumericCharacterSet.

The docs for +alphanumericCharacterSet

A character set containing the characters in the categories Letters, Marks, and 
Numbers.

So I think this means that I will have to also exclude + nonBaseCharacterSet.

The actual content of an NSCharacterSet is only accessible via 
-bitmapRepresentation which makes previewing the content slightly involved.

  Additionally, for higher-level interpreted languages the app would need to 
 understand identifier prefixes such as $, @ and % (and maybe ).

The output from this is processed through a Mustache template that takes care 
of all the variable name decoration ($, @, - and the like). 
The template will also enforce case (upper, lower, Pascal etc) and white space 
handling (remove, -, _ etc)

Thanks for the suggestions.

Jonathan
___

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: Best guess at expressing a string as a variable

2013-01-23 Thread Jean Suisse

On 23 janv. 2013, at 02:18, jonat...@mugginsoft.com jonat...@mugginsoft.com 
wrote:

 
 My current thinking is, regardless of the language, is to exclude all 
 characters that are not members of NSCharacterSet + (id)letterCharacterSet.
 
 Is  + (id)letterCharacterSet the best choice here?
 
 I don't know. Does it include characters in すごくやる気がある ?
 That is the question. I don't know what range of character ranges + 
 letterCharacterSet includes.
 A better question might be what is the intended use of + letterCharacterSet. 
 Is it locale dependent?
 
That's a fair question. As Jens Alfke pointed out yesterday, the doc states:

Return value: A character set containing the characters in the categories 
Letters and Marks.
Discussion : Informally, this set is the set of all characters used as letters 
of alphabets and ideographs.
So, it should not depend on the locale. It is however a huge set ! And I guess 
that you may not want most of it (all chinese ideograms for instance)

 
 Hmm. Maybe not. I want to keep the generated variable name legible.

 I think I will have to introduce an intermediate NSTextView that filters and 
 displays the natural language input.
 The user can then modify the variable name if necessary before it gets 
 utilised further.

Maybe you could drop the extra textfields and the processing by requesting the 
variable name to use an english alphanumeric character set ?
Otherwise, how would you deal with this input for a variable name: 名前 ? [ If I 
am a japanese user, I would expect your software to call the variable namae ].
IMHO the whole unicode character set is too large. Most language won't accept 
the largest part of the set.

Jean







---
Jean Suisse
Institut de Chimie Moléculaire de l’Université de Bourgogne
(ICMUB) — UMR 6302












___

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: Best guess at expressing a string as a variable

2013-01-23 Thread jonat...@mugginsoft.com



On 23 Jan 2013, at 11:40, Jean Suisse jean.li...@gmail.com wrote:

 On 23 janv. 2013, at 02:18, jonat...@mugginsoft.com 
 jonat...@mugginsoft.com wrote:
 
 
 My current thinking is, regardless of the language, is to exclude all 
 characters that are not members of NSCharacterSet + (id)letterCharacterSet.
 
 Is  + (id)letterCharacterSet the best choice here?
 
 I don't know. Does it include characters in すごくやる気がある ?
 That is the question. I don't know what range of character ranges + 
 letterCharacterSet includes.
 A better question might be what is the intended use of + letterCharacterSet. 
 Is it locale dependent?
 
 That's a fair question. As Jens Alfke pointed out yesterday, the doc states:
 
 Return value: A character set containing the characters in the categories 
 Letters and Marks.
 Discussion : Informally, this set is the set of all characters used as 
 letters of alphabets and ideographs.
 So, it should not depend on the locale. It is however a huge set ! And I 
 guess that you may not want most of it (all chinese ideograms for instance)
My naive thought was that I could use this admittedly huge character set. Bad 
idea.

 
 
 Hmm. Maybe not. I want to keep the generated variable name legible.
 
 I think I will have to introduce an intermediate NSTextView that filters and 
 displays the natural language input.
 The user can then modify the variable name if necessary before it gets 
 utilised further.
 
 Maybe you could drop the extra textfields and the processing by requesting 
 the variable name to use an english alphanumeric character set ?
 Otherwise, how would you deal with this input for a variable name: 名前 ? [ If 
 I am a japanese user, I would expect your software to call the variable 
 namae ].
I think that if the user enters the like of  名前 as a parameter title I will 
filter its decomposed version using the alphanumeric character set.
This will give an empty string which I will then default to something sensible.
Basically an alphanumeric approach will be, by definition, very tough on non 
alphabetic input.

A Japanese speaker using the app to generate scripts will know how to program, 
hence entering some alpha numerics should be trivial.
A Japanese speaker using the app just to execute the script will see the 名前 
parameter title only.

Thanks for the suggestions.

Jonathan
___

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: Best guess at expressing a string as a variable

2013-01-23 Thread Uli Kusterer

On Jan 23, 2013, at 2:18 AM, jonat...@mugginsoft.com wrote:
Hmm. Maybe not. I want to keep the generated variable name legible.

You need to nail down the languages you want to deploy to, and then find out
what their criteria for identifiers are. Then you can decide to either generate
identical lowest-common-denominator-names for all of them (which is
[a-zA-Z_]([a-zA-Z_0-9]*) in the case of C, i.e. it may not start with a number
either), or adjust what characters to permit based on the target programming
language.

Apart from character set, you may also have to be aware of length limits etc.
Early C compilers, for instance, only used the first 8 characters of an
identifier. So ExceptionalHouse and ExceptionalCow both ended up as the
same identifier, Exceptio. I'm hard pressed to think of a language with such
a limit today, but I don't know what languages your targeting. Maybe one has
such a limit.

If you have a case where you can't express a character in a particular
character set, you have several options:

1) Transcribe it to an equivalent character set. E.g. U-Umlaut (ü) is usually
written as ue. However, you will then have to deal with collisions. E.g. what
if one user enters the word Frauen, but another makes up a new word Fraün.
The latter would transcribe to the former, and you might get unexpected side
effects. You might have to generate a look-up-table, and if you find a
collision like that, make the name unique again, e.g. by naming one frauen
and the other frauen2. IIRC there are official transcriptions for many
languages, e.g. Romanji for Japanese characters.

2) Fail and tell the user what the valid characters are, and only let them
enter valid characters.

Is + (id)letterCharacterSet the best choice here?

According to the docs
(https://developer.apple.com/library/mac/#documentation/Cocoa/Reference/Foundation/Classes/NSCharacterSet_Class/Reference/Reference.html):
An NSCharacterSet object represents a set of Unicode-compliant characters.
The +letterCharacterSet documentation says Returns a character set containing
the characters in the categories Letters and Marks. So a Google later, here
http://www.fileformat.info/info/unicode/category/index.htm the categories
mentioning Letters include greek characters, accented characters, hiragana
and cyrillic characters among others (most of which are invalid as C identifier
names). Oddly, marks seem to include some kind of punctuation. I couldn't
find a section that is obviously only letters and marks or two separate
letters and marks sections.

Anyway, I think building your own custom character set from a string including
the characters you *know* are valid identifiers in your target programming
language(s) is probably the route of least surprise.

Cheers,
-- Uli Kusterer
The Witnesses of TeachText are everywhere...
http://hammer-language.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: How to avoid warning?

2013-01-23 Thread Uli Kusterer

On Jan 22, 2013, at 8:12 PM, Jens Alfke j...@mooseyard.com wrote:
 @interface SomeFictionalClassName
 - (id) initWithManager: (Foo*)manager;
 @end

That feels a bit dirty to me. I'd recommend using a protocol instead. As long 
as the compiler has seen the method *somewhere*, it will consider it having 
been declared. So

@protocol AvoidCompilerWarning
- (id) initWithManager: (Foo*)manager;
@end

is, for the purposes of this particular discussion, equivalent to Jens's 
fictional class interface, but doesn't imply that such a class might exist to a 
(human) reader.

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

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

Re: How to avoid warning?

2013-01-23 Thread Uli Kusterer


On Jan 22, 2013, at 8:28 PM, Andy Lee ag...@mac.com wrote:
 To be extra fail-safe, you might want to perform a cast to be sure the right 
 initWithManager: gets called:
 
 if ([myClass conformsToProtocol:@protocol(MyProtocol)])
   myObj = [(id MyProtocol)[myClass alloc] initWithManager:self];
 else
   myObj = [[myClass alloc] init];


 This only works for classes that actually declare themselves to be in 
conformance with this protocol, though. Even if a class implements all the 
methods in a protocol, conformsToProtocol: will return NO if it doesn't have 
the protocol name on the @interface (or on the @implementation line).

IMO the nicest way to do this (if you can't make all your classes conform to 
the protocol by declaring them as @interface Foo : NSObject 
UKCanInitWithManagerProtocol, which would definitely be the cleanest 
approach), would be:

@protocol UKCanInitWithManagerProtocol
-(id)   initWithManager: (Foo*)inManager;
@end

...

if( [myClass respondsToSelector: @selector(initWithManager:)] )
myObj = [(idUKCanInitWithManagerProtocol)[myClass alloc] 
initWithManager: self];
else
myObj = [[myClass alloc] init];

Though I would recommend choosing a different name. E.g. -initWithBarManager: 
if the manager class is called UKBarManager. Manager alone is too generic a 
word, and someone might have declared it in ObjC++ and taking a C++ object and 
then you're screwed.

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

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

Re: Best guess at expressing a string as a variable

2013-01-23 Thread jonat...@mugginsoft.com

On 23 Jan 2013, at 13:07, Uli Kusterer witness.of.teacht...@gmx.net wrote:

On Jan 23, 2013, at 2:18 AM, jonat...@mugginsoft.com wrote:
Hmm. Maybe not. I want to keep the generated variable name legible.

You need to nail down the languages you want to deploy to, and then find out
what their criteria for identifiers are. Then you can decide to either
generate identical lowest-common-denominator-names for all of them (which is
[a-zA-Z_]([a-zA-Z_0-9]*) in the case of C, i.e. it may not start with a
number either), or adjust what characters to permit based on the target
programming language.
This is known http://www.mugginsoft.com/kosmictask/help/languages.
The app uses a plugin-architecture so more may appear.

Apart from character set, you may also have to be aware of length limits etc.
Early C compilers, for instance, only used the first 8 characters of an
identifier. So ExceptionalHouse and ExceptionalCow both ended up as the
same identifier, Exceptio. I'm hard pressed to think of a language with
such a limit today, but I don't know what languages your targeting. Maybe one
has such a limit.
The plugin defines the language properties so length constraints can be
included.
Som experimentation will determine the limits.

If you have a case where you can't express a character in a particular
character set, you have several options:

1) Transcribe it to an equivalent character set. E.g. U-Umlaut (ü) is usually
written as ue. However, you will then have to deal with collisions. E.g.
what if one user enters the word Frauen, but another makes up a new word
Fraün. The latter would transcribe to the former, and you might get
unexpected side effects. You might have to generate a look-up-table, and if
you find a collision like that, make the name unique again, e.g. by naming
one frauen and the other frauen2. IIRC there are official transcriptions
for many languages, e.g. Romanji for Japanese characters.

2) Fail and tell the user what the valid characters are, and only let them
enter valid characters.

3) Transcribe in some other way, e.g. by base64-encoding, or using a
hex-representation of the given byte sequence, or whatever. This way you
could keep ASCII sentences valid, but modify everything else. But even then
you could have collisions. E.g. if you replace spaces with underscores, what
if there's a second version with the underscore?
I was intending to decompose U-Umlaut (ü) to u + Umlaut and then discard the
umlaut if possible. Or perhaps an API exists to decompose the likes of U-Umlaut
(ü) to ue.
I already have collision detection code that appends integers for uniqueness.

Is + (id)letterCharacterSet the best choice here?

According to the docs
(https://developer.apple.com/library/mac/#documentation/Cocoa/Reference/Foundation/Classes/NSCharacterSet_Class/Reference/Reference.html):
An NSCharacterSet object represents a set of Unicode-compliant characters.
The +letterCharacterSet documentation says Returns a character set
containing the characters in the categories Letters and Marks. So a Google
later, here http://www.fileformat.info/info/unicode/category/index.htm
Thanks for the link. I didn't know that the categories were specified by
unicode. I had assumed they were arbitrarily defined by Apple.

the categories mentioning Letters include greek characters, accented
characters, hiragana and cyrillic characters among others (most of which are
invalid as C identifier names). Oddly, marks seem to include some kind of
punctuation. I couldn't find a section that is obviously only letters and
marks or two separate letters and marks sections.
I see that. Anyhow, I can have a look at the likes of +nonBaseCharacterSet and
see how they correlate exactly with the Unicode categories.

Anyway, I think building your own custom character set from a string
including the characters you *know* are valid identifiers in your target
programming language(s) is probably the route of least surprise.

Agree.
I want to get a sensible wide base and restrict it on a per language basis.

Thanks for such a detailed reply.

Jonathan
___

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: How to avoid warning?

2013-01-23 Thread Andy Lee

On Jan 23, 2013, at 8:22 AM, Uli Kusterer witness.of.teacht...@gmx.net wrote:
 @protocol UKCanInitWithManagerProtocol
 -(id) initWithManager: (Foo*)inManager;
 @end
 
 ...
 
 if( [myClass respondsToSelector: @selector(initWithManager:)] )
   myObj = [(idUKCanInitWithManagerProtocol)[myClass alloc] 
 initWithManager: self];
 else
   myObj = [[myClass alloc] init];

Well, the extra-super-defensive approach would be to not only check 
respondsToSelector:, but to check that the method signature of the object's 
implementation matches what's declared in the protocol. :)

But yeah, you can't rely on conformsToProtocol: if you don't have the luxury of 
making the relevant classes conform to the protocol.

--Andy

___

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: Best guess at expressing a string as a variable

2013-01-23 Thread Fritz Anderson

On 23 Jan 2013, at 5:40 AM, Jean Suisse jean.li...@gmail.com wrote:

 
 Hmm. Maybe not. I want to keep the generated variable name legible.
 
 I think I will have to introduce an intermediate NSTextView that filters and 
 displays the natural language input.
 The user can then modify the variable name if necessary before it gets 
 utilised further.
 
 Maybe you could drop the extra textfields and the processing by requesting 
 the variable name to use an english alphanumeric character set ?
 Otherwise, how would you deal with this input for a variable name: 名前 ? [ If 
 I am a japanese user, I would expect your software to call the variable 
 namae ].
 IMHO the whole unicode character set is too large. Most language won't accept 
 the largest part of the set.

Would CFStringTransform() be of comfort in this situation? There is the problem 
that ideographs get mapped from Mandarin. Good choice in terms of (potential) 
user base; for now a poor choice for a technical user base.

Oops, the function also takes ICU transliteration transforms (though I'd be 
impressed if it took all of them). The fully reversible transforms yield 
Latin with diacritics, but there seems to be an option to smash them. 

— F

-- 
Fritz Anderson
Xcode 4 Unleashed: 4.5 supplement for free!
http://www.informit.com/store/xcode-4-unleashed-9780672333279


___

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

NSComboBox, binding, multiple selection, multiple values == trouble

2013-01-23 Thread Markus Spoettl


Hello,

  in my app, I can edit a selection of model objects in a window which that 
consists of NSTextFields and NSComboBoxes to edit model properties, all via 
binding to an NSArrayController's selection proxy.


When I'm editing a multi-selection that has property values are different for 
individual model objects in the selection, I get an undesired behavior from 
NSComboBox:


When I tab over an NSComboBox which displays the multiple-values placeholder, 
upon exiting the combo box, the corresponding property for all selected objects 
is nil'd. (BAD)


When I do the same (tabbing over) with an NSTextField, the values of the 
individual objects' properties are unchanged. (GOOD).


Since I have no control over how NSComboBox implements its bindings and I 
therefore can't fix the handling of multi-valued selections, I fixed this by 
subclassing NSComboBox and implementing -objectValue by returning the 
NSMultipleValuesMarker object as I see fit.


- (id)objectValue
{
id result = [super objectValue];
if (returnMultiValuesMarkerForEmptyObjectValue) {
if ([result isEqualTo:@])  {
result = NSMultipleValuesMarker;
}
}
return result;
}

The private returnMultiValuesMarkerForEmptyObjectValue ivar is set to YES 
externally by my editor controller which knows that a multiple selection is 
being edited.


This works reasonably well but I wonder how others have fixed this problem. I 
feel returning NSMultipleValuesMarker is a hack which works only because 
NSComboBox thinks it's a legitimate return value (or doesn't care). The fact 
that I can't clear properties for multiple selections is a side effect I can 
live with.


Any better fixes for this?

Regards
Markus
--
__
Markus Spoettl
___

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: Using NSSavePanel to export to UTTypeFolder without a file extension.

2013-01-23 Thread Thomas Bunch

Following up on my own question, NSSavePanel can be made to “work” under 
PowerBox with a UTI that has no file extension, but it does get upset with 
itself and fail an assertion when it elects to automatically turn on the hide 
extension checkbox in response to the user changing the file type. The 
exception is appended below. The default assertion handler just logs it and 
everything seems to work, though I do worry that we're not getting a proper 
reply to the request.

Updated source here: 
https://www.dropbox.com/s/qjgnpee644c5eo3/NSSavePanel-kUTTypeFolder.zip

I'll be filing a radar if bugreporter comes back up.

Highlighted changes since I last posted:
  - I had neglected to set a code signing identity, so the example wasn't 
actually sandboxed before.
  - added the com.apple.security.files.user-selected.read-write entitlement
  - declared exportable formats as NSExportableTypes using real UTIs rather 
than the old school NSExportableAs wherein I was using CFBundleTypeMIMETypes 
completely wrong anyway.

Here is the assertion that fails. Should you wish to download and build the 
project the steps to reproduce the assertion are as follows:

 - in Finder preferences, turn off Show all filename extensions
 - build and run the project
 - File - Export…, 
 - switch the File Format. The hide extension checkbox will turn on. Turn it 
off.
 - repeat the previous step as necessary. This seems to be a race condition and 
may take many tries.

2013-01-23 11:21:35.728 NSSavePanel-kUTTypeFolder[26816:303] *** Assertion 
failure in -[NSRemoteSavePanel connection:didReceiveRequest:], 
/SourceCache/RemoteViewServices/RemoteViewServices-80.5/NSRemoteSavePanel.m:1713
2013-01-23 11:21:35.730 NSSavePanel-kUTTypeFolder[26816:303] caught exception {
name = NSInternalInconsistencyException;
reason = window allowed unexpectedly;
} during request {requestType: 15, connections: 0, ports: 0, arguments: {
NSRemotePanelRequestKVOStateDidChangeNewStateKey = 1;
NSRemotePanelRequestKVOStateDidChangePathKey = isExtensionHidden;
}} with call stack (
0   CoreFoundation  0x7fff8a9e30a6 
__exceptionPreprocess + 198
1   libobjc.A.dylib 0x7fff8baca3f0 
objc_exception_throw + 43
2   CoreFoundation  0x7fff8a9e2ee8 
+[NSException raise:format:arguments:] + 104
3   Foundation  0x7fff86ae96a2 
-[NSAssertionHandler handleFailureInMethod:object:file:lineNumber:description:] 
+ 189
4   RemoteViewServices  0x7fff85bf3dc1 
-[NSRemoteSavePanel connection:didReceiveRequest:] + 131
5   RemoteViewServices  0x7fff85bec73f 
__block_global_4 + 68
6   CoreFoundation  0x7fff8a9a0272 
__CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ + 18
7   CoreFoundation  0x7fff8a960a4f 
__CFRunLoopDoBlocks + 255
8   CoreFoundation  0x7fff8a985220 
__CFRunLoopRun + 1904
9   CoreFoundation  0x7fff8a9846b2 
CFRunLoopRunSpecific + 290
10  AppKit  0x7fff860fb14b 
-[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 150
11  AppKit  0x7fff85de846f -[NSMenu 
_internalPerformActionForItemAtIndex:] + 36
12  AppKit  0x7fff85de82f7 
-[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 135
13  AppKit  0x7fff860f4245 
NSSLMMenuEventHandler + 342
14  HIToolbox   0x7fff8904af0a 
_ZL23DispatchEventToHandlersP14EventTargetRecP14OpaqueEventRefP14HandlerCallRec 
+ 1206
15  HIToolbox   0x7fff8904a3d9 
_ZL30SendEventToEventTargetInternalP14OpaqueEventRefP20OpaqueEventTargetRefP14HandlerCallRec
 + 410
16  HIToolbox   0x7fff890601bd 
SendEventToEventTarget + 40
17  HIToolbox   0x7fff89096e89 
_ZL18SendHICommandEventjPK9HICommandjjhPKvP20OpaqueEventTargetRefS5_PP14OpaqueEventRef
 + 443
18  HIToolbox   0x7fff8903bc11 
SendMenuCommandWithContextAndModifiers + 59
19  HIToolbox   0x7fff8903bbc3 
SendMenuItemSelectedEvent + 254
20  HIToolbox   0x7fff8903ba4f 
_ZL19FinishMenuSelectionP13SelectionDataP10MenuResultS2_ + 94
21  HIToolbox   0x7fff891b2009 
_ZL19PopUpMenuSelectCoreP8MenuData5PointdS1_tjPK4RecttjS4_S4_PK10__CFStringPP13OpaqueMenuRefPt
 + 1673
22  HIToolbox   0x7fff891b1924 
_HandlePopUpMenuSelection7 + 629
23  AppKit  0x7fff8617761b 
_NSSLMPopUpCarbonMenu3 + 3916
24  AppKit  0x7fff864d8d2a

Re: NSComboBox, binding, multiple selection, multiple values == trouble

2013-01-23 Thread Quincey Morris

On Jan 23, 2013, at 09:28 , Markus Spoettl ms_li...@shiftoption.com wrote:

  in my app, I can edit a selection of model objects in a window which that 
 consists of NSTextFields and NSComboBoxes to edit model properties, all via 
 binding to an NSArrayController's selection proxy.
 
 When I'm editing a multi-selection that has property values are different for 
 individual model objects in the selection, I get an undesired behavior from 
 NSComboBox:
 
 When I tab over an NSComboBox which displays the multiple-values placeholder, 
 upon exiting the combo box, the corresponding property for all selected 
 objects is nil'd. (BAD)

Does the Allows Editing Multiple Values Selection binding option, if 
unchecked, prevent the problem?


___

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: NSComboBox, binding, multiple selection, multiple values == trouble

2013-01-23 Thread Markus Spoettl


On 1/23/13 9:51 PM, Quincey Morris wrote:

When I'm editing a multi-selection that has property values are different for
individual model objects in the selection, I get an undesired behavior from
NSComboBox:

When I tab over an NSComboBox which displays the multiple-values placeholder,
upon exiting the combo box, the corresponding property for all selected
objects is nil'd. (BAD)


Does the Allows Editing Multiple Values Selection binding option, if
unchecked, prevent the problem?


No.

Allows Editing Multiple Values Selection ON or OFF doesn't change the behavior 
(clearing multi-value content on exit). Conditionally Sets Editable ON makes 
it non-editable for multi-value content if Allows Editing Multiple Values 
Selection is OFF, which is not what I want.


Regards
Markus
--
__
Markus Spoettl
___

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: NSComboBox, binding, multiple selection, multiple values == trouble

2013-01-23 Thread Keary Suska

On Jan 23, 2013, at 10:28 AM, Markus Spoettl wrote:

  in my app, I can edit a selection of model objects in a window which that 
 consists of NSTextFields and NSComboBoxes to edit model properties, all via 
 binding to an NSArrayController's selection proxy.
 
 When I'm editing a multi-selection that has property values are different for 
 individual model objects in the selection, I get an undesired behavior from 
 NSComboBox:
 
 When I tab over an NSComboBox which displays the multiple-values placeholder, 
 upon exiting the combo box, the corresponding property for all selected 
 objects is nil'd. (BAD)
 
 When I do the same (tabbing over) with an NSTextField, the values of the 
 individual objects' properties are unchanged. (GOOD).

I had a similar issue and I don't think it has anything to do with the binding. 
It seems to be that NSCombobox always sets the value as displayed when the 
field is exited regardless of whether the contents have been edited or not. So, 
if the contents are nil, it will set the value(s) to nil on exit. This may be 
an acceptable outcome when editing a single value, so it is probably 
overlooked. In my case it was unnecessarily dirtying the document edited state. 
My solution was to scrap comboboxes and instead use regular NSTextFields with 
autocompletion support provided by a formatter. It proved to be actually better 
in my situation--more intuitive to the user. Of course, these were fields whose 
possible contents are already known by the user, such as a name prefix (Mr Ms 
etc)

 Since I have no control over how NSComboBox implements its bindings and I 
 therefore can't fix the handling of multi-valued selections, I fixed this by 
 subclassing NSComboBox and implementing -objectValue by returning the 
 NSMultipleValuesMarker object as I see fit.
 
 - (id)objectValue
 {
id result = [super objectValue];
if (returnMultiValuesMarkerForEmptyObjectValue) {
if ([result isEqualTo:@])  {
result = NSMultipleValuesMarker;
}
}
return result;
 }
 
 The private returnMultiValuesMarkerForEmptyObjectValue ivar is set to YES 
 externally by my editor controller which knows that a multiple selection is 
 being edited.
 
 This works reasonably well but I wonder how others have fixed this problem. I 
 feel returning NSMultipleValuesMarker is a hack which works only because 
 NSComboBox thinks it's a legitimate return value (or doesn't care). The fact 
 that I can't clear properties for multiple selections is a side effect I can 
 live with.

This actually works? I wouldn't think so--I would expect that all of the field 
values get set to the string value of NSMultipleValuesMarker, which is really 
what the code looks like it should be doing. If there are indeed some internals 
that are ignoring the marker, they are undocumented (AFAIK) and shouldn't be 
relied upon.

 Any better fixes for this?

If you are really dedicated to using NSCombobox, I would avoid bindings and 
instead handle it manually, using target-action. This way, when your controller 
receives the action you can check for a multiple selection and ignore it if so.

HTH,

Keary Suska
Esoteritech, Inc.
Demystifying technology for your home or business


___

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: NSComboBox, binding, multiple selection, multiple values == trouble

2013-01-23 Thread Markus Spoettl


On 1/23/13 10:25 PM, Keary Suska wrote:

This works reasonably well but I wonder how others have fixed this problem.
I feel returning NSMultipleValuesMarker is a hack which works only because
NSComboBox thinks it's a legitimate return value (or doesn't care). The
fact that I can't clear properties for multiple selections is a side effect
I can live with.


This actually works? I wouldn't think so--I would expect that all of the
field values get set to the string value of NSMultipleValuesMarker, which is
really what the code looks like it should be doing. If there are indeed some
internals that are ignoring the marker, they are undocumented (AFAIK) and
shouldn't be relied upon.


Yes, it works. My theory is that the NSArrayController, which is actually 
updating the model via its selection proxy, does the right thing when it gets a 
NSMultipleValuesMarker back as object value.



Any better fixes for this?


If you are really dedicated to using NSCombobox, I would avoid bindings and
instead handle it manually, using target-action. This way, when your
controller receives the action you can check for a multiple selection and
ignore it if so.


Yes, that may be an option, though not a very convenient one. Getting rid of 
NSComboBox altogether may be more attractive.


Regards
Markus
--
__
Markus Spoettl

___

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

New iTunes UI

2013-01-23 Thread Koko

In the album view if you select and begin to drag a view slides out from the 
right with drop destinations. The question: Is this sliding view an animated 
split view or some other form of view animation?

-koko

Sent from my iPad
___

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: New iTunes UI

2013-01-23 Thread Graham Cox


On 24/01/2013, at 3:40 AM, Koko k...@highrolls.net wrote:

 The question: Is this sliding view an animated split view or some other form 
 of view animation?


It definitely doesn't look like a split view, since it appears on top of the 
underlying view, not alongside. It's probably just another view.

--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: Coordinate conversions in CALayer

2013-01-23 Thread Graham Cox


On 23/01/2013, at 5:41 PM, Graham Cox graham@bigpond.com wrote:

 To create a transform that supposedly will transform from the superlayer TO 
 the layer, and I then invert it to go back the other way. It works in the 
 simple case, but a rotation transform upsets things. I've tried pretty much 
 every combination of ordering different things in constructing the transform 
 but this is the best result I get. Still wrong though. Funny, every time I 
 think I have transforms figured out something turns up to show me I don't.



Boiling down my problem to its bare essentials, why are these two bits of code 
not equivalent?


CGPoint anch = layer.anchorPoint;
CGRect  br = layer.bounds;
CGPoint pos = layer.position;

CGContextTranslateCTM( ctx, pos.x, pos.y );
CGContextConcatCTM( ctx, layer.transform );
CGContextTranslateCTM(ctx, -(br.origin.x + anch.x * br.size.width), 
-(br.origin.y + anch.y * br.size.height));

The above works correctly, but below, which I thought should do the same, does 
not, if the layer.transform property is not the identity matrix:


CGPoint anch = layer.anchorPoint;
CGRect  br = layer.bounds;
CGPoint pos = layer.position;


CGAffineTransform tfm = CGAffineTransformMakeTranslation( pos.x, pos.y 
);
tfm = CGAffineTransformConcat( tfm, layer.transform );
tfm = CGAffineTransformTranslate( tfm, -(br.origin.x + anch.x * 
br.size.width), -(br.origin.y + anch.y * br.size.height));

CGContextConcatCTM( ctx, tfm );

In the second case I've tried every combination of ordering the different 
statements that build the transform, and the sign of the translations, but 
nothing I have tried makes the second code work identically to the first. I'm 
missing something obvious but I'm not grokking it. I need the second case to 
work because it is needed in other situations where I have no context - e.g. 
just performing transformation calculations between a layer and its superlayer.

Please someone help, this is driving me bats.

--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: Coordinate conversions in CALayer

2013-01-23 Thread Quincey Morris

On Jan 23, 2013, at 17:01 , Graham Cox graham@bigpond.com wrote:

 The above works correctly, but below, which I thought should do the same, 
 does not, if the layer.transform property is not the identity matrix:
 
 
   CGPoint anch = layer.anchorPoint;
   CGRect  br = layer.bounds;
   CGPoint pos = layer.position;
 
   
   CGAffineTransform tfm = CGAffineTransformMakeTranslation( pos.x, pos.y 
 );
   tfm = CGAffineTransformConcat( tfm, layer.transform );
   tfm = CGAffineTransformTranslate( tfm, -(br.origin.x + anch.x * 
 br.size.width), -(br.origin.y + anch.y * br.size.height));
   
   CGContextConcatCTM( ctx, tfm );
 
 In the second case I've tried every combination of ordering the different 
 statements that build the transform, and the sign of the translations, but 
 nothing I have tried makes the second code work identically to the first. I'm 
 missing something obvious but I'm not grokking it. I need the second case to 
 work because it is needed in other situations where I have no context - e.g. 
 just performing transformation calculations between a layer and its 
 superlayer.
 
 Please someone help, this is driving me bats.

This sort of thing drives me nuts too. You have to simplify the problem.

1. In the scenario where bounds.origin is (0,0) and the anchor point is (0,0) 
-- which should be be a very ordinary scenario to set up, even if you have to 
abuse your app to make it so -- the third transformation has no effect. If -- 
another ordinary scenario (I'd hope) -- the layer transform is the identity, 
the second transformation has no effect. So start with those scenarios in 
effect. Can you make it work with *just* the first translation doing something? 
That will incidentally settle the sign question once and for all.

2. Once you have that working, start using a non-identity layer transform, 
preferably something very easy like a 90 degree rotation, or a 50% scale, or a 
reflection about a vertical axis. If you don't get the right answer, it 
*should* be obvious why not. Then try it with a 30 degree rotation to check you 
didn't just solve it for a special case.

(If you're depending on seeing what draws to find out if you got it right, try 
something like a 95% or a 105% scale. One or other of those would likely still 
draw something you can recognize, and tell you whether the error is a 
mis-translation or a mis-scale, and in which direction.)

3. After you get that far, I can't imagine it would be difficult to get the 
last transformation right. Even so, do it in 2 parts, first with a non-zero 
bounds origin, then second with a different anchor point.

As to why the methodology isn't precisely parallel in the 2 cases, I dunno, but 
I suspect it's because in one case you're drawing untransformed geometry into a 
transformed drawing space; in the other case, you're drawing transformed 
geometry into an untransformed drawing space. Those two things might be as 
equivalent as you expect.

But you've probably thought this all through already ...
___

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

NSAttributedString boundingRectWithSize vs. paragraph margins

2013-01-23 Thread Matt Neuburg

The docs on boundingRectWithSize:options:context: say:

  Typically, the renderer preserves the width constraint and adjusts the 
height constraint as needed.

Yes, that's what I was hoping for. But in fact I'm getting a much narrower 
width than what I supplied.

I suspect that the problem here has to do with differing expectations as to 
what bounding rect means, and as to what my paragraph margins mean. Here's 
some more complete code:

NSString* sentence = @This is a test. ;
NSString* s = @;
for (int i = 0; i  20; i++)
s = [s stringByAppendingString:sentence];
NSMutableParagraphStyle* mps = [NSMutableParagraphStyle new];
mps.headIndent = 20;
mps.firstLineHeadIndent = 20;
mps.tailIndent = -20;
NSAttributedString* as = [[NSAttributedString alloc] initWithString:s 
attributes:@{
  NSParagraphStyleAttributeName:mps
  }];
CGRect r = [as boundingRectWithSize:CGSizeMake(100,1) 
options:NSStringDrawingUsesLineFragmentOrigin context:nil];
NSLog(@%@, NSStringFromCGRect(r));

The resulting width is 51.8. So it looks as if that's the width *after* the 
margins (20 and 20) have squeezed the text inward. What we're getting, it 
seems, is the minimum bounding rect containing any text. But that's not what I 
want to know; I want to know the height of this text as drawn within the width 
I supplied (100) using the paragraph margins I supplied. Is there some other 
way to find that out? Or is this a bug with regard to how margins are 
interpreted? m.


--
matt neuburg, phd = m...@tidbits.com, http://www.apeth.net/matt/
pantes anthropoi tou eidenai oregontai phusei
Programming iOS 5! http://shop.oreilly.com/product/0636920023562.do
RubyFrontier! http://www.apeth.com/RubyFrontierDocs/default.html
TidBITS, Mac news and reviews since 1990, http://www.tidbits.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 update the UI from sheetDidEnd:…. ?

2013-01-23 Thread Nick Rogers

Hi,

I was updating a few textfields from my sheetDidEnd:…. method.
Just wondering if that was causing the crash (UI related error in main thread).

Thanks,
Nick
___

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: Issue with Core Data Mapping Model

2013-01-23 Thread John Brayton

Yes, the hashes do change when I add the model mapping.

I ended up writing an NSEntityMigrationPolicy for a parent object that copies
these child entities.

In addition, I also opened up a DTS incident with Apple. The gentleman from
Apple observed that I had an interesting difference between model versions:

* In the prior version, I had an entity that was optional and had a minimum and
maximum count set to 1.
* In the newer version, the minimum count was not set.

It is odd that the minimum and maximum values even exist, since the
relationship in question is not a to-many relationship. I honestly don't know
if I set these values or if Xcode did that for me. At any rate, setting the
minimum count back to 1 seemed to make the mapping model recognized by Core
Data.

I hope this helps you.

John

On Jan 22, 2013, at 12:12 PM, Sean McBride s...@rogue-research.com wrote:

On Thu, 17 Jan 2013 21:45:51 -0500, John Brayton said:

I am building a mapping model between two versions of my Core Data
model, and I am encountering a strange issue:

* If I define six of the seven entity mappings I need in the mapping
model, migrating the data works as expected.

* When I add the seventh entity mapping, the migration fails with this error:
Persistent store migration failed, missing mapping model.

* If I delete that seventh entity mapping, the migration works again.

* I am trying to do the migration by calling addPersistentStoreWithType:
… on the NSPersistentStoreCoordinator.

* Reading in both the source and destination models with
NSManagedObjectModel initWithContentsOfURL:... works as expected.

* Reading in the NSMappingModel with initWithContentsOfURL:… works as
expected.

* With the seventh entity mapping added, reading in the mapping model
with [NSMappingModel mappingModelFromBundles:@[bundle]
forSourceModel:source destinationModel:dest] returns null.

This sounds a lot like something I am seeing. Do you see hash mismatches
like described here:

http://stackoverflow.com/questions/10894383/core-data-mapping-model-version-hashes-not-matching-to-source-model-version-hash

I've spent hours on it, and as best as I can tell Xcode is generating invalid
xcmappingmodel files. Just the other day I've used a DTS incident on this,
but have not heard back yet. I'll follow up in this thread when I do.

Cheers,

Sean McBride, B. Eng s...@rogue-research.com
Rogue Researchwww.rogue-research.com
Mac Software Developer Montréal, Québec, Canada
On Jan 22, 2013, at 12:12 PM, Sean McBride s...@rogue-research.com wrote: