Clone SipSelect

Hi,

Does anyone know how I can clone sipselect? It used to be an .exe,
which is easy enough to clone.

If I read the common makefile correctly, it now seems to be a part of
commctrl; but I don't want to clone that too. So I would like to
overwrite the sipselect.lib at the correct moment in the build process.

The way it is now, I only have sipselect.lib files under the
public/common tree, and I don't want to overwrite those files. I want
to overwrite them in the cesysgen folder, but how can I tell commctrl
to use my lib and not the public one?

Regards,
Piet

Paul
Mon Apr 10 10:56:37 CDT 2006

What's the actual goal of this operation? What, rather than how, are you
trying to do? I guess I should point out that you didn't indicate Windows
CE version, either...

Paul T.

"Piet" <pietdesomere@yahoo.com> wrote in message
news:1144684147.879170.37840@g10g2000cwb.googlegroups.com...
> Hi,
>
> Does anyone know how I can clone sipselect? It used to be an .exe,
> which is easy enough to clone.
>
> If I read the common makefile correctly, it now seems to be a part of
> commctrl; but I don't want to clone that too. So I would like to
> overwrite the sipselect.lib at the correct moment in the build process.
>
> The way it is now, I only have sipselect.lib files under the
> public/common tree, and I don't want to overwrite those files. I want
> to overwrite them in the cesysgen folder, but how can I tell commctrl
> to use my lib and not the public one?
>
> Regards,
> Piet
>

Piet
Tue Apr 11 04:43:52 CDT 2006

Sorry, CE version 5.0. A customer has asked to add a close button to
the sip (in the system bar, not in the client window - I have proposed
that). I suppose this would only involve a small change to the
CreateWindow call and to the WndProc. I can't do it from the IM
implementation, I have to change sipselect (or at least so I think).

I'm not sure if I will do it in the end (it would affect all SIPs, not
sure if I want that). But I would like to demonstrate it.

regards,
Piet

Piet
Tue Apr 11 04:53:54 CDT 2006

Sorry, CE version 5.0. A customer has asked to add a close button to
the sip (in the system bar, not in the client window - I have proposed
that). I suppose this would only involve a small change to the
CreateWindow call and to the WndProc. I can't do it from the IM
implementation, I have to change sipselect (or at least so I think).

I'm not sure if I will do it in the end (it would affect all SIPs, not
sure if I want that). But I would like to demonstrate it.

regards,
Piet

Paul
Tue Apr 11 10:58:52 CDT 2006

I suppose that you could try, in IInputMethod::Select(), changing the style
(and the location, etc., etc.), of the parent window. This seems like a
generally bad idea, though. One more potentially incompatible change to the
OS. If he doesn't understand closing the SIP, that seems like more of a
training issue than something that ought to be addressed by changing the
operating system.

Paul T.

"Piet" <pietdesomere@yahoo.com> wrote in message
news:1144741350.850652.221960@t31g2000cwb.googlegroups.com...
> Sorry, CE version 5.0. A customer has asked to add a close button to
> the sip (in the system bar, not in the client window - I have proposed
> that). I suppose this would only involve a small change to the
> CreateWindow call and to the WndProc. I can't do it from the IM
> implementation, I have to change sipselect (or at least so I think).
>
> I'm not sure if I will do it in the end (it would affect all SIPs, not
> sure if I want that). But I would like to demonstrate it.
>
> regards,
> Piet
>

Piet
Wed Apr 12 02:22:29 CDT 2006

There are several ways to close the sip, I have explained this and yet
the customer asks if it is possible to have a close button there. If
this is not a big deal I would like to show it to him and let him
decide, rather than telling him what is best for him.

To do it from the client window is, as you say, not a good idea. To
call adding a close button to the sipselect "changing the operating
system" seems a bit exaggerated to me. Which brings me back to the
first question: does anyone know how I can clone sipselect? If it is a
bad idea as such, let me know why, and I don't do it.

Regards,
Piet

Paul
Wed Apr 12 11:49:40 CDT 2006

You *are* changing the OS. You have to modify the SIP driver to change how
it a) calculates window sizes, b) chooses styles for the window, c) add code
to process the close indication from the close button, d) handles doing all
this *without* becoming the focused window, since you can't be 'activated'
or the keys that you're sending won't go where you want them to go.

Paul T.

"Piet" <pietdesomere@yahoo.com> wrote in message
news:1144826549.357094.79600@u72g2000cwu.googlegroups.com...
> There are several ways to close the sip, I have explained this and yet
> the customer asks if it is possible to have a close button there. If
> this is not a big deal I would like to show it to him and let him
> decide, rather than telling him what is best for him.
>
> To do it from the client window is, as you say, not a good idea. To
> call adding a close button to the sipselect "changing the operating
> system" seems a bit exaggerated to me. Which brings me back to the
> first question: does anyone know how I can clone sipselect? If it is a
> bad idea as such, let me know why, and I don't do it.
>
> Regards,
> Piet
>

Piet
Thu Apr 13 02:20:46 CDT 2006

Thanks for the answers, Paul.

I thought it would have been as simple as creating the window with the
WS_SYSMENU style, and adding the WM_CLOSE message to the MainWndProc,
making it use the same code as IDM_SIP_HIDE. Would this not work
because of the WS_EX_NOACTIVATE style?

Piet

Paul
Thu Apr 13 12:22:56 CDT 2006

It wouldn't necessarily work because that affects the window size (the
window size has to be bigger to contain the keyboard client, as well as the
new title bar, etc.) There's also handling for WM_CLOSE that it doesn't
really ever use right now, which might do what you want and might not, etc.,
etc. There are a huge number of assumptions built into the way that SIP
management works. You have to get lucky and find and work around them all.
Be my guest and try to redo it. It's certainly an interesting exercise, but
I don't see it as particularly valuable.

Paul T.

"Piet" <pietdesomere@yahoo.com> wrote in message
news:1144912846.772845.305320@z34g2000cwc.googlegroups.com...
> Thanks for the answers, Paul.
>
> I thought it would have been as simple as creating the window with the
> WS_SYSMENU style, and adding the WM_CLOSE message to the MainWndProc,
> making it use the same code as IDM_SIP_HIDE. Would this not work
> because of the WS_EX_NOACTIVATE style?
>
> Piet
>

Piet
Fri Apr 14 03:09:27 CDT 2006

Thanks for the information, in that case I will gladly pass and tell
the customer that unfortunately it will be impossible :-)

Regards,
Piet