#49 S60 UI doesn't work well with talks app

[John Covici]

Once you get connected tothe host -- Talks does not
read the screen at all. Talks is a voice app which reads
the contents of most screens for Symbian 60 phones.
This is probably due to standard controls not being used
i.e. read only edit boxes or whatever.

[Petteri Kangaslampi]

Logged In: YES
user_id=930478

Yes, this is because the terminal window uses a custom
control that doesn't support whatever Talks tries to use to
read the screen.

I suspect this could be solved by a more complete
MCoeFepAwareTextEditor implementation, but I haven't had
time to look into it. I haven't really seen any
documentation on what an application should do to be
compatible with Talks.

[Nobody/Anonymous]

Logged In: NO

Well, instead of a custom control could you change it to a standard one
such as a read only edit box? If you tell me where this is used I would be willing
do work on it. I have the ability to compile under Linux, although I am new to
this API.

[Petteri Kangaslampi]

Logged In: YES
user_id=930478

I doubt that standard controls would work as such, since the
terminal view has a lot of special requirements, including
custom fonts. However, it might be possible to maintain a
shadow copy in an invisible CEikEdwin or something similar
for FEP purposes. I expect a more complete FEP-awareness
implementation is a better idea though.

The terminal control base class is in
ui/common/terminalcontrol.cpp and terminalcontrol.h. The S60
version uses terminalcontrols2font.* in the same directory.

I suspect the most important MCoeFepAwareTextEditor methods
are DocumentLengthForFep(), GetCursorSelectionForFep(), and
GetEditorContentForFep(). These currently have a fairly
minimal implementation that works with S60 multitap input
and partially (but not fully) with T9.