[news.eclipse.technology.ercp] Re: Virtual Keyboard handling spec

["Mark Rogalski" <rogalski@xxxxxxxxxx>]

Several suggestions have been made to improve this JavaDoc. First off, there 
is no guarantee that all devices will have virtual keyboards. A device with 
a real keyboard does not need a virtual one. And also, some platforms may 
not allow precise control of  the virtual keyboard. Therefore, I specified 
that the 3 argument values are hints.
Secondly, since VK_NORMAL mode just allows the native OS to perform its 
default behavior in regard to displaying a virtual keyboard,. We can not 
guarantee precisely which widgets will automatically show the virtual 
keyboard when they get focus. Therefore, I rephrased the JavaDoc to be less 
precise about "widgets cable of text input".

The new spec is checked in to CVS.

"Mark Rogalski" <rogalski@xxxxxxxxxx> wrote in message 
news:e54aie$prv$1@xxxxxxxxxxxxxxxxxxxx
>I just discovered that I had never added the new MobileDevice.setVKStatus() 
>method to the MobileExtensions spec. But in adding this now, I realized 
>that we have made an error regarding the constants used for this API. The 
>original proposal added new constants to the Device class (thinking the 
>constants will also be used by Core widgets). This is a bad idea, since 
>eRCP apps written to use these new constants will not be able to compile 
>against Desktop SWT which does not contain these constants. This is a 
>violation of our agreement to keep eSWT a strict subset of SWT in order to 
>maintain upward compatability.
>
> Therefore, I propose puting the new constants in MobileDevice. See the 
> spec below and please return comments.
>
> /**
>
> * Sets the status of the system virtual keyboard (if one is available).
>
> * By default, or when status is set to VK_NORMAL, a system virtual 
> keyboard
>
> * is displayed when a widget capable of text input gains focus and is
>
> * hidden when that widget looses focus. However, there are cases where
>
> * an application may wish to continuously display the virtual keyboard
>
> * or always keep it hidden. Setting the status to VK_ALWAYS_ON or 
> VK_ALWAYS_OFF
>
> * will accomplish this and the effect is immediate. Changing focus will
>
> * then have no affect on the virtual keyboard. Note: By default, widgets 
> which
>
> * normally accept input but are set to <i>read only</i> do not cause the
>
> * the virtual keyboard to display.
>
> *
>
> * @param status virtual keyboard mode. One of VK_NORMAL, VK_ALWAYS_ON, 
> VK_ALWAYS_OFF
>
> *
>
> * @exception IllegalArgumentException <ul>
>
> * <li>ERROR_INVALID_ARGUMENT - if the status parameter is not valid</li>
>
> * </ul>
>
> *
>
> * @see #VK_NORMAL
>
> * @see #VK_ALWAYS_ON
>
> * @see #VK_ALWAYS_OFF
>
> */
>
> public void setVKStatus(int status) {}
>
>