Hi,

On our platform, the user will typically have a keyboard. Usually, this
keyboard is a full ASCII and numeric unit, so there's no need for a SIP.
However, there are situations where a user might have only a numeric
keyboard and want the SIP for rare alpha input (an operator's name, maybe,
entered once per day).

So, I don't want the SIP popping up, by default, any time an EDIT field is
selected, but I don't want to completely remove SIP support. My initial
strategy for this was to implement my own SIP, which would be the default.
This default SIP would do nothing (no window popup, no resizing of dialogs,
etc.) When this SIP was selected, then, it would be very much like having
no SIP at all in the system (design goal #1 met). However, the user (or the
user's application), could change the active SIP, if it wanted SIP input,
and could then easily pop the SIP up or down at the right times (design goal
#2 met).

However, it turns out that none of the logical ways I tried to implement
this SIP will cause this to happen. I've tried having the SIP return E_FAIL
from its Select() method. This causes the SIP not to have a UI, but also
seems to disable the other SIPs from doing anything. I've tried returning
error codes from other methods, also. I've tried having the Showing()
method call various of the APIs available to the SIP, asking that it be
closed, but this doesn't work correctly (the frame window around the SIP is
still displayed, although it has no client content). I've also done this
for the Select() and other methods.

Since I don't have source for the SOFTKB component, I'm out of ideas as to
how to achieve my goals. Does anyone know of a DeviceIoControl() for the
SOFTKB driver, other API function, a registry entry, or insider's trick that
will allow me to either prevent the SIP from appearing, or cause it to
immediately pop back down without disabling SIP input completely?

Paul T.

Re: SIP disable by bill

bill
Mon Jul 28 18:28:41 CDT 2003

I haven't tried this, but I was making my own SIP today so reading more of
the help.

Function SipSetInfo takes a SIPINFO structure which has a field fdwFlags
which says it can enable/disable the SIP.

This is different from SipShowIM which is the show/hide function frequently
used.

"Paul G. Tobey [eMVP]" <ptobey_no_spam@instrument.com> wrote in message
news:epHfTBVVDHA.2272@TK2MSFTNGP10.phx.gbl...
> Hi,
>
> On our platform, the user will typically have a keyboard. Usually, this
> keyboard is a full ASCII and numeric unit, so there's no need for a SIP.
> However, there are situations where a user might have only a numeric
> keyboard and want the SIP for rare alpha input (an operator's name, maybe,
> entered once per day).
>
> So, I don't want the SIP popping up, by default, any time an EDIT field is
> selected, but I don't want to completely remove SIP support. My initial
> strategy for this was to implement my own SIP, which would be the default.
> This default SIP would do nothing (no window popup, no resizing of
dialogs,
> etc.) When this SIP was selected, then, it would be very much like having
> no SIP at all in the system (design goal #1 met). However, the user (or
the
> user's application), could change the active SIP, if it wanted SIP input,
> and could then easily pop the SIP up or down at the right times (design
goal
> #2 met).
>
> However, it turns out that none of the logical ways I tried to implement
> this SIP will cause this to happen. I've tried having the SIP return
E_FAIL
> from its Select() method. This causes the SIP not to have a UI, but also
> seems to disable the other SIPs from doing anything. I've tried returning
> error codes from other methods, also. I've tried having the Showing()
> method call various of the APIs available to the SIP, asking that it be
> closed, but this doesn't work correctly (the frame window around the SIP
is
> still displayed, although it has no client content). I've also done this
> for the Select() and other methods.
>
> Since I don't have source for the SOFTKB component, I'm out of ideas as to
> how to achieve my goals. Does anyone know of a DeviceIoControl() for the
> SOFTKB driver, other API function, a registry entry, or insider's trick
that
> will allow me to either prevent the SIP from appearing, or cause it to
> immediately pop back down without disabling SIP input completely?
>
> Paul T.
>
>



Re: SIP disable by Paul

Paul
Mon Jul 28 18:37:45 CDT 2003

I've given that a try, both from the Select() method and the Showing()
method. The outline of the actual SIP top-level window is not hidden,
although the Hiding() method *does* get called. Let me know if you spot
anything else that might work!

Paul T.

"bill" <poddw@yahoo.com> wrote in message
news:eOP8y$VVDHA.1052@TK2MSFTNGP09.phx.gbl...
> I haven't tried this, but I was making my own SIP today so reading more of
> the help.
>
> Function SipSetInfo takes a SIPINFO structure which has a field fdwFlags
> which says it can enable/disable the SIP.
>
> This is different from SipShowIM which is the show/hide function
frequently
> used.
>
> "Paul G. Tobey [eMVP]" <ptobey_no_spam@instrument.com> wrote in message
> news:epHfTBVVDHA.2272@TK2MSFTNGP10.phx.gbl...
> > Hi,
> >
> > On our platform, the user will typically have a keyboard. Usually, this
> > keyboard is a full ASCII and numeric unit, so there's no need for a SIP.
> > However, there are situations where a user might have only a numeric
> > keyboard and want the SIP for rare alpha input (an operator's name,
maybe,
> > entered once per day).
> >
> > So, I don't want the SIP popping up, by default, any time an EDIT field
is
> > selected, but I don't want to completely remove SIP support. My initial
> > strategy for this was to implement my own SIP, which would be the
default.
> > This default SIP would do nothing (no window popup, no resizing of
> dialogs,
> > etc.) When this SIP was selected, then, it would be very much like
having
> > no SIP at all in the system (design goal #1 met). However, the user (or
> the
> > user's application), could change the active SIP, if it wanted SIP
input,
> > and could then easily pop the SIP up or down at the right times (design
> goal
> > #2 met).
> >
> > However, it turns out that none of the logical ways I tried to implement
> > this SIP will cause this to happen. I've tried having the SIP return
> E_FAIL
> > from its Select() method. This causes the SIP not to have a UI, but
also
> > seems to disable the other SIPs from doing anything. I've tried
returning
> > error codes from other methods, also. I've tried having the Showing()
> > method call various of the APIs available to the SIP, asking that it be
> > closed, but this doesn't work correctly (the frame window around the SIP
> is
> > still displayed, although it has no client content). I've also done
this
> > for the Select() and other methods.
> >
> > Since I don't have source for the SOFTKB component, I'm out of ideas as
to
> > how to achieve my goals. Does anyone know of a DeviceIoControl() for
the
> > SOFTKB driver, other API function, a registry entry, or insider's trick
> that
> > will allow me to either prevent the SIP from appearing, or cause it to
> > immediately pop back down without disabling SIP input completely?
> >
> > Paul T.
> >
> >
>
>



Re: SIP disable by mike

mike
Wed Jul 30 08:56:21 CDT 2003

Paul,

What platform are you on?

I don't have any of the issues you suggest with either
pocketpc or ce.net 4.0/1

I think that on pocketpc (just found that it's ce.net too)
it's a case of the app using the SHSipPreference to
SIP_DOWN
or it setting the SHSipInfo with the flags set to SIP_OFF.

neither way seems to nee you programming a special sip,
just getting the app ( or a special app) to define the SIP
usage.

Am I missing the point?

regards,

Mike

>-----Original Message-----
>I've given that a try, both from the Select() method and
the Showing()
>method. The outline of the actual SIP top-level window
is not hidden,
>although the Hiding() method *does* get called. Let me
know if you spot
>anything else that might work!
>
>Paul T.
>
>"bill" <poddw@yahoo.com> wrote in message
>news:eOP8y$VVDHA.1052@TK2MSFTNGP09.phx.gbl...
>> I haven't tried this, but I was making my own SIP today
so reading more of
>> the help.
>>
>> Function SipSetInfo takes a SIPINFO structure which has
a field fdwFlags
>> which says it can enable/disable the SIP.
>>
>> This is different from SipShowIM which is the show/hide
function
>frequently
>> used.
>>
>> "Paul G. Tobey [eMVP]" <ptobey_no_spam@instrument.com>
wrote in message
>> news:epHfTBVVDHA.2272@TK2MSFTNGP10.phx.gbl...
>> > Hi,
>> >
>> > On our platform, the user will typically have a
keyboard. Usually, this
>> > keyboard is a full ASCII and numeric unit, so there's
no need for a SIP.
>> > However, there are situations where a user might have
only a numeric
>> > keyboard and want the SIP for rare alpha input (an
operator's name,
>maybe,
>> > entered once per day).
>> >
>> > So, I don't want the SIP popping up, by default, any
time an EDIT field
>is
>> > selected, but I don't want to completely remove SIP
support. My initial
>> > strategy for this was to implement my own SIP, which
would be the
>default.
>> > This default SIP would do nothing (no window popup,
no resizing of
>> dialogs,
>> > etc.) When this SIP was selected, then, it would be
very much like
>having
>> > no SIP at all in the system (design goal #1 met).
However, the user (or
>> the
>> > user's application), could change the active SIP, if
it wanted SIP
>input,
>> > and could then easily pop the SIP up or down at the
right times (design
>> goal
>> > #2 met).
>> >
>> > However, it turns out that none of the logical ways I
tried to implement
>> > this SIP will cause this to happen. I've tried
having the SIP return
>> E_FAIL
>> > from its Select() method. This causes the SIP not to
have a UI, but
>also
>> > seems to disable the other SIPs from doing anything.
I've tried
>returning
>> > error codes from other methods, also. I've tried
having the Showing()
>> > method call various of the APIs available to the SIP,
asking that it be
>> > closed, but this doesn't work correctly (the frame
window around the SIP
>> is
>> > still displayed, although it has no client content).
I've also done
>this
>> > for the Select() and other methods.
>> >
>> > Since I don't have source for the SOFTKB component,
I'm out of ideas as
>to
>> > how to achieve my goals. Does anyone know of a
DeviceIoControl() for
>the
>> > SOFTKB driver, other API function, a registry entry,
or insider's trick
>> that
>> > will allow me to either prevent the SIP from
appearing, or cause it to
>> > immediately pop back down without disabling SIP input
completely?
>> >
>> > Paul T.
>> >
>> >
>>
>>
>
>
>.
>

Re: SIP disable by Paul

Paul
Wed Jul 30 13:23:50 CDT 2003

I think you're missing the point. I want to have a configuration 'setting'
that is not specific to a particular application that 'turns off' the SIP.
That is, no matter what application is popped up and no matter what it does,
the SIP stays down. We're a hardware manufacturer, providing a tool for
software developers in the field. I'd like to enable them to use a SIP, if
they are creating a UI that might need it for some reason, but I don't want
to saddle everyone else, who doesn't need it and, frankly, finds it
annoying, with a keyboard popping up all over the place.

I wasn't able to use SHSipPreference() to turn SIP popup off globally and
the same is true of calling SHSipInfo() from inside my custom SIP.
Obviously, a given application can turn the SIP off, but Explorer, for
example, turns it on by default, so I need a global way to control that
without having to recode everything.

Paul T.

"mike" <no@thanks> wrote in message
news:0d2b01c356a2$5b708fa0$a301280a@phx.gbl...
> Paul,
>
> What platform are you on?
>
> I don't have any of the issues you suggest with either
> pocketpc or ce.net 4.0/1
>
> I think that on pocketpc (just found that it's ce.net too)
> it's a case of the app using the SHSipPreference to
> SIP_DOWN
> or it setting the SHSipInfo with the flags set to SIP_OFF.
>
> neither way seems to nee you programming a special sip,
> just getting the app ( or a special app) to define the SIP
> usage.
>
> Am I missing the point?
>
> regards,
>
> Mike
>
> >-----Original Message-----
> >I've given that a try, both from the Select() method and
> the Showing()
> >method. The outline of the actual SIP top-level window
> is not hidden,
> >although the Hiding() method *does* get called. Let me
> know if you spot
> >anything else that might work!
> >
> >Paul T.
> >
> >"bill" <poddw@yahoo.com> wrote in message
> >news:eOP8y$VVDHA.1052@TK2MSFTNGP09.phx.gbl...
> >> I haven't tried this, but I was making my own SIP today
> so reading more of
> >> the help.
> >>
> >> Function SipSetInfo takes a SIPINFO structure which has
> a field fdwFlags
> >> which says it can enable/disable the SIP.
> >>
> >> This is different from SipShowIM which is the show/hide
> function
> >frequently
> >> used.
> >>
> >> "Paul G. Tobey [eMVP]" <ptobey_no_spam@instrument.com>
> wrote in message
> >> news:epHfTBVVDHA.2272@TK2MSFTNGP10.phx.gbl...
> >> > Hi,
> >> >
> >> > On our platform, the user will typically have a
> keyboard. Usually, this
> >> > keyboard is a full ASCII and numeric unit, so there's
> no need for a SIP.
> >> > However, there are situations where a user might have
> only a numeric
> >> > keyboard and want the SIP for rare alpha input (an
> operator's name,
> >maybe,
> >> > entered once per day).
> >> >
> >> > So, I don't want the SIP popping up, by default, any
> time an EDIT field
> >is
> >> > selected, but I don't want to completely remove SIP
> support. My initial
> >> > strategy for this was to implement my own SIP, which
> would be the
> >default.
> >> > This default SIP would do nothing (no window popup,
> no resizing of
> >> dialogs,
> >> > etc.) When this SIP was selected, then, it would be
> very much like
> >having
> >> > no SIP at all in the system (design goal #1 met).
> However, the user (or
> >> the
> >> > user's application), could change the active SIP, if
> it wanted SIP
> >input,
> >> > and could then easily pop the SIP up or down at the
> right times (design
> >> goal
> >> > #2 met).
> >> >
> >> > However, it turns out that none of the logical ways I
> tried to implement
> >> > this SIP will cause this to happen. I've tried
> having the SIP return
> >> E_FAIL
> >> > from its Select() method. This causes the SIP not to
> have a UI, but
> >also
> >> > seems to disable the other SIPs from doing anything.
> I've tried
> >returning
> >> > error codes from other methods, also. I've tried
> having the Showing()
> >> > method call various of the APIs available to the SIP,
> asking that it be
> >> > closed, but this doesn't work correctly (the frame
> window around the SIP
> >> is
> >> > still displayed, although it has no client content).
> I've also done
> >this
> >> > for the Select() and other methods.
> >> >
> >> > Since I don't have source for the SOFTKB component,
> I'm out of ideas as
> >to
> >> > how to achieve my goals. Does anyone know of a
> DeviceIoControl() for
> >the
> >> > SOFTKB driver, other API function, a registry entry,
> or insider's trick
> >> that
> >> > will allow me to either prevent the SIP from
> appearing, or cause it to
> >> > immediately pop back down without disabling SIP input
> completely?
> >> >
> >> > Paul T.
> >> >
> >> >
> >>
> >>
> >
> >
> >.
> >