Re: [E-devel] The problem of the parameter in ecore_imf_context_input_mode_set

[Carsten H. (T. R. <ra...@ra...>]

On Fri, 18 Mar 2011 20:21:45 +0900 Jihoon Kim <jih...@sa...> said:

> Hello,
> 
> I think there are a problem of parameter in
> ecore_imf_context_input_mode_set().
> 
> The second parameter of that API can be combined more than an enum value
> such ECORE_IMF_INPUT_MODE_HEXA | ECORE_IMF_MODE_TELE.
> 
> It is weird. In this situation (HEXA | TELE), Which layout should the
> virtual keyboard show?
> The concept of combination makes us confused.
> 
> If there is no special reason that we should use this API, I'd like to add
> the new API.

well that api defines a list of properties of the input as a bitmask. some
combinations just don't make sense. also look at it this way. it's a request.
it's a "please, i'd like... X, Y and Z". the input method can say "well sorry.
only got X and Y. too bad. no Z's in stock". so if it is given nonsensical
combinations it can just filter them out and choose whatever it feels is best.
there are some bitmasks missing there like "URL", and "EMAIL_ADDR", "TERM" and
so on (URL entry mode, email address entry mode, terminal type entry (unix
terminal, so provide more control chars like a full keyboard if possible) etc.
etc.). we can just accept that certain modes in combination make no sense, and
anyone requesting input should ONLY set the bits they REALLY want or need and
not go setting useless extra bits in case.

-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler)    ra...@ra...