Hello all,
the usual print machinery (NSPrintOperation) for a Cocoa-based
text editor (TextEdit, say) allows one to use a variety of page layouts.
Unfortunately, in many cases the only layout available to the user
involves a considerable waste of paper space, and this does not seem
to be fixable
Hello all,
in the user interface of my Cocoa app I have a button with two
alternative titles,
one that I write in Interface Builder and the other appears on a line in
my code as
follows,
[theButton setTitle:[NSString stringWithFormat:@"Put a n with a
tilde,like this
>
> You want %C, not %c (%c is "character", while %C is unicode character).
>
You're right, it works now with %C instead of %c. Thanks! I guess the use
of %c should be avoided, like the use of old-fashioned C Strings?
Ewan
_
>
> "%c" is interpreted at runtime according to the default string
> encoding for that process. This depends on what the user's preferred
> language is set to, but for English and most European languages it's
> MacRoman. That choice makes sense for backward-compatibility reasons,
> but nowadays it
Hello all,
I'm trying to construct a Cocoa app that mimicks the Mail application,
with the difference
that it's not especially intended for mails : one the upper part a list of
titles, and on the lower
part exactly one title&text is shown. Double-clicking on a title in the
upper part makes
>Perhaps you have a good reason, but from your description, and being
>used to using Mail, I'd expect the lower part to display the content
>with a single click.
The reason is, I know how to produce easily the "double-click" behaviour
with Cocoa but not the (better) "click" behaviour
>Good qu
>>I'm not quite sure what you mean by "target" here
>The "target" is the object that your selector message will be sent to.
>How will your TableView know which object responds to the selector you
>give it? It's not magic...
>HTH
It did help indeed, and even solved my problem! (it now
Corbinn Dunn wrote
I'm not quite sure what you mean by "target" here
>>> The "target" is the object that your selector message will be sent
>>> to.
>>> How will your TableView know which object responds to the selector
>>> you
>>> give it? It's not magic...
>>> HTH
>>
>> It did hel
Hello all,
I have a Cocoa app that performs some computations on
large integers (but still in the "unsigned long long" range), some
of which are entered by the user in a NSTextField.
The problem , of course, is that NSControl has no
-(unsigned long long)unsignedLongLongValue metho
Thanks Ken and Steve,
for the variety of clean solutions you offered. Just out of
curiosity, I should like to return to a point mentioned by
Ken :
>If you must work character-by-character,
>use character constants (e.g. >'0' or '9')
In that (unlikely) situation, how would I test, say, equali
10 matches
Mail list logo
