I NSTextView I can display glyphs which have no Unicode representation
following Technical Note TN2079.
But how to do this in a WebView?
Kind regards,
Gerriet.
___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin request
I want to display glyphs which do NOT have a Unicode representation.
Currently I use Font Book.app to search for the Glyph and then code (following
suggestions in Technical Note TN2079):
NSGlyph glyphNbr;
NSString *familyName = [ font familyName ];
if ( [ fam
On Nov 18, 2011, at 15:21 , patrick machielse wrote:
> I need to _continuously_ merge changes made in the _main_ thread into a
> context held by a background thread. Most (all?) discussions about
> multi-threading in CoreData discuss merging changes from a _finite_ operation
> in the _backgroun
On Nov 18, 2011, at 18:48, Roland King wrote:
>
> On Nov 19, 2011, at 10:38 AM, Conrad Shultz wrote:
>
>> On 11/18/11 3:29 PM, Laurent Daudelin wrote:
>>> There isn't much special code in that UITableView subclass and not
>>> much either in the UITableViewController so I'm a little bit at a
>>>
On Nov 19, 2011, at 10:38 AM, Conrad Shultz wrote:
> On 11/18/11 3:29 PM, Laurent Daudelin wrote:
>> There isn't much special code in that UITableView subclass and not
>> much either in the UITableViewController so I'm a little bit at a
>> lost as to what could cause this. There is nothing fancy
On 11/18/11 3:29 PM, Laurent Daudelin wrote:
> There isn't much special code in that UITableView subclass and not
> much either in the UITableViewController so I'm a little bit at a
> lost as to what could cause this. There is nothing fancy here, no
> custom handling of touches and things like that
I forgot to add to my previous message that the scrollview will resume its
dragging momentum if I touch and drag any other view.
Does that give a clue to anyone?
Thanks!
-Laurent.
--
Laurent Daudelin
AIM/iChat/Skype:LaurentDaudelin
http://www.nemesys-soft.com/
Hello.
I'm facing the task of fixing a problem occurring in one of the UITableView of
our app. The view displays cells of various height. Everything works fine,
except that we have a mechanism that when we reach the last cell at the bottom,
that cell will trigger loading more data and adding mo
I'm struggling a bit with multi-threading approaches for CoreData…
I need to _continuously_ merge changes made in the _main_ thread into a context
held by a background thread. Most (all?) discussions about multi-threading in
CoreData discuss merging changes from a _finite_ operation in the _back
On Nov 18, 2011, at 9:23 AM, Richard Somers wrote:
> The normal pattern for Interface Builder Outlets is assign but I have an
> outlet that must be retained to work corectly. The outlet is not in File's
> Owner but is in a custom view in a window.
>
> // Interface
> @property (retain) IBOutlet
On Fri, Nov 18, 2011 at 1:47 PM, Charles Srstka
wrote:
> How is one supposed to manage this? You can easily get the array of the
> top-level objects, but since ARC doesn’t let you send -release to them, it
> doesn’t help much. The only ways I can think of to avoid leaking are to do
> silly thin
Okay, I know you’re supposed to use the likes of NSWindowController and
NSViewController to load nibs, since they will automatically take care of
releasing the top-level objects. However, for the sake of curiosity, I created
a new project with ARC just to see what would happen with NSNib. The pr
I have a Xcode 4.2 project with a dozen or so nibs. I'm in the process
of assuring that all the resizing is set up properly.
I find that a small number of primary views - the one attached to the
"view" outlet - have "fixed" autoresizing masks, and while I can set or
unset the four outter attac
On Nov 18, 2011, at 1:33 PM, Corbin Dunn wrote:
> You are probably orphaning (which is a leak), your window controller
> subclass. Make sure it's dealloc is called; I'm guessing it won't be. This
> isn't shown in "leaks", since it isn't a true leak.
Good suggestion. I just checked and the windo
You are probably orphaning (which is a leak), your window controller subclass.
Make sure it's dealloc is called; I'm guessing it won't be. This isn't shown in
"leaks", since it isn't a true leak.
corbin
On Nov 18, 2011, at 11:22 AM, Richard Somers wrote:
> On Nov 18, 2011, at 9:31 AM, Kyle Slu
On Nov 18, 2011, at 12:42 PM, Kyle Sluder wrote:
> It means that NSWindowController will balance NSNib's extra -retain.
> It doesn't balance the additional -retain from calling your setter.
Consider the following case. The additional -retain from calling setter is not
balanced. The outlet is not
On Fri, Nov 18, 2011 at 11:22 AM, Richard Somers
wrote:
> The outlet in question is in a custom class and requires a setter with retain
> semantics. NSWindowController will use this setter for the outlet when
> loading the nib.
NSWindowController does not call your setter. NSNib does.
>
> Obje
On Nov 18, 2011, at 9:31 AM, Kyle Sluder wrote:
> On Fri, Nov 18, 2011 at 8:23 AM, Richard Somers wrote:
>> The normal pattern for Interface Builder Outlets is assign but I have an
>> outlet that must be retained to work corectly. The outlet is not in File's
>> Owner but is in a custom view in a
Le 18 nov. 2011 à 19:45, Kyle Sluder a écrit :
> Yes, that would indeed be true. I just assumed you were adding the
> image rep to an NSImage and using -[NSImage drawInRect::].
I considered that for a while, but since -drawInRect exists for
NSBitmapImageRep, I thought it was useless.
Beside
On Fri, Nov 18, 2011 at 8:50 AM, vincent habchi wrote:
> Kyle,
>
>> Re-read the "NSImage: deprecating -[NSImage setFlipped:], adding a
>> drawing method that respects context flippedness" section of the 10.6
>> AppKit release notes to make sure you're correctly using the "flipped"
>> property and
Kyle,
> Re-read the "NSImage: deprecating -[NSImage setFlipped:], adding a
> drawing method that respects context flippedness" section of the 10.6
> AppKit release notes to make sure you're correctly using the "flipped"
> property and the respectFlipped: argument to -drawInRect:: :
I’ve tried
On Fri, Nov 18, 2011 at 6:18 AM, Vincent Habchi wrote:
> PS : Of course, a workaround is to flip the view coordinates thus:
>
> [myView translateOriginToPoint:NSMakePoint(0, [self frame].size.height)];
> [myView scaleUnitSquareToSize:NSMakeSize(1, -1)];
>
> but it still does not explain why -drawI
On Fri, Nov 18, 2011 at 8:23 AM, Richard Somers
wrote:
> The normal pattern for Interface Builder Outlets is assign but I have an
> outlet that must be retained to work corectly. The outlet is not in File's
> Owner but is in a custom view in a window.
It is very important that you specify wheth
The normal pattern for Interface Builder Outlets is assign but I have an outlet
that must be retained to work corectly. The outlet is not in File's Owner but
is in a custom view in a window.
// Interface
@property (retain) IBOutlet NSArrayController *myController;
// Implementation
@synthesize
PS : Of course, a workaround is to flip the view coordinates thus:
[myView translateOriginToPoint:NSMakePoint(0, [self frame].size.height)];
[myView scaleUnitSquareToSize:NSMakeSize(1, -1)];
but it still does not explain why -drawInRect:fromRect:…hints: seems to ignore
the hints.
Vincent
Hi there,
I’m trying to draw a flipped NSImageBitmapRep object (data comes out of an
OpenGL depth buffer) in a NSView. I thought I could set up an appropriate
affine transform (x’ = x, y’ = height - y), embed it in a dictionary and put
that in the hints parameter of a -drawInRect:fromRect:…hin
There is the Nuance SDK you could use. Requires Internet access though. It
rocks hard.
Eric
Sent from my iPhone
On Nov 18, 2011, at 6:47 AM, Luca Ciciriello
wrote:
> Hi All
>
> Is there in iOS 5 something like COCOA NSSpeechSynthesizer to be used to
> read some text on iPhone?
>
> Thank
Hi All
Is there in iOS 5 something like COCOA NSSpeechSynthesizer to be used to read
some text on iPhone?
Thanks for any answer.
Luca.___
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to
Le 18 nov. 2011 à 11:59, Jean-Daniel Dupas a écrit :
>
> Le 18 nov. 2011 à 10:59, Nicholas Francis a écrit :
>
>> Problem with Xcode >4 is that this is the same build farm that compiles out
>> standalone executable which has compatibility down to Tiger, so we're stuck
>> on Xcode 3.x versions
Le 18 nov. 2011 à 10:59, Nicholas Francis a écrit :
> Problem with Xcode >4 is that this is the same build farm that compiles out
> standalone executable which has compatibility down to Tiger, so we're stuck
> on Xcode 3.x versions (at least for the next 8 months or so). Superannoying,
> but t
On Nov 16, 2011, at 1:51 PM, Patrick Robertson wrote:
> AXUIElementPostKeyboardEvent (app, (CGCharCode) 0, (CGKeyCode)55, true );
> //Command
>
> AXUIElementPostKeyboardEvent (app, (CGCharCode) 0, (CGKeyCode)53, true );
> //Escape
>
> AXUIElementPostKeyboardEvent (app, (CGCharCode) 0, (CGKeyCod
Problem with Xcode >4 is that this is the same build farm that compiles out
standalone executable which has compatibility down to Tiger, so we're stuck on
Xcode 3.x versions (at least for the next 8 months or so). Superannoying, but
that's what we get for making a dev tool that will target ancie
32 matches
Mail list logo
