Thanks a lot to everyone. I not only got rid of the
extra text box from my dialog UI but also learnt few
things :)
> If you could have dictated back then that no
> TEHandle to be used,
> your editable fields wouldn't work. The point I want
> to make is that
> you shouldn't even ask this kind of question.
> Instead of asking how
> to do some low level hack you think you need to
> address something,
> you should ask for the best way to address the
> higher level problem.
I meant how to get the extra non-unicode text box out
of my UI. In my dialog UI I used to get 2 blinking
cursors, one for the Unicode text and another of the
shared field editor ( as Mr. Kusterer pointed out).
Now all I have to do is to just deactivate the
TEHandle for my dialog box as follows...
-----------------------------------------------------
TEHandle teHandle =
GetDialogTextEditHandle(dialogRef) ;
TEDeactivate ( teHandle );
-----------------------------------------------------
>
> - Why are you replacing static text controls? There
> aren't two
> versions of static text controls. The static text
> control created
> when the dialog is created supports Unicode text.
>
The reason I have to replace the static text resource
item with static text control is that static text
resource item cannot be updated using CFString as they
can be used with SetDialogItemText() which doesn't
accept unicode characters.
Thanks again for the inputs.
Shri
--- Laurence Harris <email@hidden> wrote:
>
> On May 22, 2007, at 7:21 AM, Shrinidhi Karanth
> wrote:
>
> > However, I cannot change my design to use
> > some compositing resources or not to use resources
> at
> > all since it is tightly coupled with the rest of
> the
> > project.
>
> Well, this late in the game the whole project needs
> to come into the
> present. ;-)
>
> > Would like to know if there is anyway I can
> > turn off the shared field editor! Is there a way
> to
> > dictate that no TEHandle to be used for my dialog
> > window?
>
> Fortunately this question is not applicable in Mac
> OS X. However, if
> the common TEHandle *were* still being used, this
> question makes no
> sense. The thing you're asking if you can turn off
> is the mechanism
> the Dialog Manager used to handle editable text
> fields in a dialog.
> If you could have dictated back then that no
> TEHandle to be used,
> your editable fields wouldn't work. The point I want
> to make is that
> you shouldn't even ask this kind of question.
> Instead of asking how
> to do some low level hack you think you need to
> address something,
> you should ask for the best way to address the
> higher level problem.
> The two best answers are:
>
> - Switch to nibs.
>
> - Define the text fields with 'CNTL' resources using
> the appropriate
> proc ID for an Edit Unicode Text control.
>
> Larry
>
____________________________________________________________________________________
8:00? 8:25? 8:40? Find a flick in no time
with the Yahoo! Search movie showtime shortcut.
http://tools.search.yahoo.com/shortcuts/#news
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Carbon-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
