current version of UnicodeData.txt and parse it.
> But this looks not very efficient.
>
> For punctuation one could use NSCharacterSet punctuationCharacterSet.
>
> But for Math Symbols?
>
> I did look at CFStringTransform, which can give the Character name via
> kCFS
b
CPPFLAGS: -I/include
hope it will help
ask me off-list if you have any problem
cheers
dm
> On Jul 7, 2015, at 9:10 AM, Gerriet M. Denkmann wrote:
>
>
>> On 7 Jul 2015, at 19:33, Dmitry Markman wrote:
>>
>> ICU’s
>>
>> u_charType
>
&
re identical in most
locales, but in some locales they differ. For example, the pattern
"#,##,###" formats the number 123456789 as "12,34,56,789".
• The pad specifier padSpec may appear before the prefix, after the
prefix, before the suffix, after the suffix, or not at al
7;t get any warning about recognising selector
some settings of my project are
SDKROOT = $(DEVELOPER_SDK_DIR)/MacOSX10.5.sdk
MACOSX_DEPLOYMENT_TARGET = 10.5
I have
Xcode 3.0
Mac OS X 10.5.3
thanks
Dmitry Markman
___
Cocoa-dev mailing list (Cocoa-dev@li
indeed
thanks a lot
it works now
On Jun 15, 2008, at 5:13 PM, Ken Thomases wrote:
On Jun 15, 2008, at 3:57 PM, Dmitry Markman wrote:
Hi, all
I have a problem with the NSMutableAttributedString's
setBaseWritingDirection method
here is a code
NSMutableAttributedS
eviously (10.3.X) responder wasn't the same: it could be
NSTextView or NSTextField or something different
but now it is always WebHTMLView (something undocumented I suppose)
anybody can say what could be a problem?
thank you very much in advance
Dmitry Markman
_
hange, but keyboard works
interesting that I'm getting mouseDidMoveOverElement message
thanks again
dm
On Mar 16, 2008, at 1:45 AM, Jens Alfke wrote:
On 15 Mar '08, at 9:39 PM, Dmitry Markman wrote:
I remember, previously (10.3.X) responder wasn't the same: it could
be NST
:"Hello
From Cocoa" encoding:NSMacOSRomanStringEncoding];
without any warnings about _NSAutoreleaseNoPool
so I suppose default NSAutoreleasePool was created for me
so how I can verify it?
thanks
Dmitry Markman
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.
On 4 Apr 2008, at 02:03, Dmitry Markman wrote:
Hi
How can I tell that default autorelease pool exists?
Dmitry
The default autorelease pool is created in the .m file
of a newly created project. If you have messed around too much with
that file, you might have deleted it.
The interesting line
amish Allan wrote:
On Fri, Apr 4, 2008 at 1:03 AM, Dmitry Markman <[EMAIL PROTECTED]>
wrote:
but from other hand in the complex Carbon application, where I never
explicitly created NSAutoreleasePool object
I can call
NSString *textString = [NSString
stringWithCString:"H
g anything that could autorelease objects, and there might not
be a pool already, create your own by calling [NSAutoreleasePool
new] beforehand and [pool drain] afterwards.
—Jens
Dmitry Markman
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Plea
Just addition to the previous email
On Apr 3, 2008, at 9:45 PM, Dmitry Markman wrote:
[stringAttributes release];
[font release];
[cocoaColor release];
[context release];
[textString release];
[nsFontName release];
[pool release];
if I
er playing with those releases I found that only
[font release];
[nsFontName release];
are harmless
it looks like that they were cached
it doesn't make any sense to me (at least yet :-( )
it looks like that solution is to go to GarbageCollection and forget
SString stringWithCString:"Hello
From Cocoa" encoding:NSMacOSRomanStringEncoding];
can not
so what's the difference?
thanks
On Apr 3, 2008, at 10:10 PM, Rob Keniger wrote:
On 04/04/2008, at 11:54 AM, Dmitry Markman wrote:
if I comment all those releases (excerpt [pool release
as Jens answered, there is no way to say
On Apr 3, 2008, at 10:24 PM, stephen joseph butler wrote:
On Thu, Apr 3, 2008 at 9:18 PM, Dmitry Markman <[EMAIL PROTECTED]>
wrote:
I just thought that all those 5 methods are CREATION methods they
are not
GET methods
so how do I know
utableCopy " (again not good enough)
and release the pool
thank you very much to all who answered
On Apr 3, 2008, at 10:32 PM, Chris Suter wrote:
On 04/04/2008, at 1:25 PM, Dmitry Markman wrote:
how can you explain that
NSString *nsFontName
#x27;s "dead": doesn't respond to any event and it's not flashing
as a default button (it's just a blue button)
also in the console I can see
2008-04-16 07:09:46.800 Gateways[57273:882b] NSView is wrapped by
HIView but dra
not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/dmarkman%40mac.com
This email sent to [EMAIL PROTECTED]
Dmitry Markman
__
18 matches
Mail list logo