The "Wireless UI" does not implement in function
AdapterIPProperties (\Netui\network.c).

But the CE 5.0 document always says "Implements the IP
Properties dialog box that is displayed in the network
connections UI that allows users to configure IP
addressing, DNS/WINS information, and wireless local area
network (LAN) settings."

What's the problem?


Bryan.

Re: Wireless UI by Paul

Paul
Mon Jan 10 09:53:34 CST 2005

I'm not sure I understand what the real question is. What's the problem or
what are you trying to accomplish that's related to this? Yes, the NETUI
folder contents provides AdapterIPProperties() implementation. The wireless
UI stuff is also provided by files in that folder.

If you are complaining about the documentation, there's a link, Send
Feedback, on each help page to report problems with it to the docs team...

Paul T.

"Bryan" <anonymous@discussions.microsoft.com> wrote in message
news:1e6601c4f6cb$5931dad0$a601280a@phx.gbl...
> The "Wireless UI" does not implement in function
> AdapterIPProperties (\Netui\network.c).
>
> But the CE 5.0 document always says "Implements the IP
> Properties dialog box that is displayed in the network
> connections UI that allows users to configure IP
> addressing, DNS/WINS information, and wireless local area
> network (LAN) settings."
>
> What's the problem?
>
>
> Bryan.



Re: Wireless UI by Bryan

Bryan
Tue Jan 11 00:06:35 CST 2005

It's right.The Wireless UI is in the folder.
But it is used only for the shell having the systray.
If I use a shell without a systray, the wireless UI will
not appear. The wireless UI can not receive any
notification without the systray.

The AdapterIPProperties( ) function does not contain a
wireless sheet any more.
You can compare the function in CE 4.1 and CE 5.0.
The part of wireless was removed.
..........................
AdapterIPProperties (HWND hWndOwner, LPTSTR
szAdapterName, BOOL fOpenWireless) // CE 4.1
AdapterIPProperties (HWND hWndOwner, LPTSTR
szAdapterName) // CE 5.0



>-----Original Message-----
>I'm not sure I understand what the real question is.
What's the problem or
>what are you trying to accomplish that's related to
this? Yes, the NETUI
>folder contents provides AdapterIPProperties()
implementation. The wireless
>UI stuff is also provided by files in that folder.
>
>If you are complaining about the documentation, there's
a link, Send
>Feedback, on each help page to report problems with it
to the docs team...
>
>Paul T.
>
>"Bryan" <anonymous@discussions.microsoft.com> wrote in
message
>news:1e6601c4f6cb$5931dad0$a601280a@phx.gbl...
>> The "Wireless UI" does not implement in function
>> AdapterIPProperties (\Netui\network.c).
>>
>> But the CE 5.0 document always says "Implements the IP
>> Properties dialog box that is displayed in the network
>> connections UI that allows users to configure IP
>> addressing, DNS/WINS information, and wireless local
area
>> network (LAN) settings."
>>
>> What's the problem?
>>
>>
>> Bryan.
>
>
>.
>

Re: Wireless UI by Paul

Paul
Tue Jan 11 13:25:11 CST 2005

Yes, that's true and has been reported as a feature request here previously
(or a bug report, maybe, since it used to do that). One possibility would
be to use the API to create your own WZC interface...

Paul T.

"Bryan" <anonymous@discussions.microsoft.com> wrote in message
news:162f01c4f7a3$b4b35cc0$a501280a@phx.gbl...
> It's right.The Wireless UI is in the folder.
> But it is used only for the shell having the systray.
> If I use a shell without a systray, the wireless UI will
> not appear. The wireless UI can not receive any
> notification without the systray.
>
> The AdapterIPProperties( ) function does not contain a
> wireless sheet any more.
> You can compare the function in CE 4.1 and CE 5.0.
> The part of wireless was removed.
> ..........................
> AdapterIPProperties (HWND hWndOwner, LPTSTR
> szAdapterName, BOOL fOpenWireless) // CE 4.1
> AdapterIPProperties (HWND hWndOwner, LPTSTR
> szAdapterName) // CE 5.0
>
>
>
>>-----Original Message-----
>>I'm not sure I understand what the real question is.
> What's the problem or
>>what are you trying to accomplish that's related to
> this? Yes, the NETUI
>>folder contents provides AdapterIPProperties()
> implementation. The wireless
>>UI stuff is also provided by files in that folder.
>>
>>If you are complaining about the documentation, there's
> a link, Send
>>Feedback, on each help page to report problems with it
> to the docs team...
>>
>>Paul T.
>>
>>"Bryan" <anonymous@discussions.microsoft.com> wrote in
> message
>>news:1e6601c4f6cb$5931dad0$a601280a@phx.gbl...
>>> The "Wireless UI" does not implement in function
>>> AdapterIPProperties (\Netui\network.c).
>>>
>>> But the CE 5.0 document always says "Implements the IP
>>> Properties dialog box that is displayed in the network
>>> connections UI that allows users to configure IP
>>> addressing, DNS/WINS information, and wireless local
> area
>>> network (LAN) settings."
>>>
>>> What's the problem?
>>>
>>>
>>> Bryan.
>>
>>
>>.
>>



Re: Wireless UI by Michel

Michel
Tue Jan 11 17:16:01 CST 2005

The easiest solution is to create a "dummy" systray. I implemented it like
that (in RDP) and call the WZC configuration dialog programatically.

Regards,


Michel Verhagen
Windows CE.NET Consultant, eMVP
PTS Software
The Netherlands


"Paul G. Tobey [eMVP]" <ptobey no spam AT no instrument no spam DOT com>
wrote in message news:Oq54%23MB%23EHA.220@TK2MSFTNGP09.phx.gbl...
> Yes, that's true and has been reported as a feature request here
> previously (or a bug report, maybe, since it used to do that). One
> possibility would be to use the API to create your own WZC interface...
>
> Paul T.
>
> "Bryan" <anonymous@discussions.microsoft.com> wrote in message
> news:162f01c4f7a3$b4b35cc0$a501280a@phx.gbl...
>> It's right.The Wireless UI is in the folder.
>> But it is used only for the shell having the systray.
>> If I use a shell without a systray, the wireless UI will
>> not appear. The wireless UI can not receive any
>> notification without the systray.
>>
>> The AdapterIPProperties( ) function does not contain a
>> wireless sheet any more.
>> You can compare the function in CE 4.1 and CE 5.0.
>> The part of wireless was removed.
>> ..........................
>> AdapterIPProperties (HWND hWndOwner, LPTSTR
>> szAdapterName, BOOL fOpenWireless) // CE 4.1
>> AdapterIPProperties (HWND hWndOwner, LPTSTR
>> szAdapterName) // CE 5.0
>>
>>
>>
>>>-----Original Message-----
>>>I'm not sure I understand what the real question is.
>> What's the problem or
>>>what are you trying to accomplish that's related to
>> this? Yes, the NETUI
>>>folder contents provides AdapterIPProperties()
>> implementation. The wireless
>>>UI stuff is also provided by files in that folder.
>>>
>>>If you are complaining about the documentation, there's
>> a link, Send
>>>Feedback, on each help page to report problems with it
>> to the docs team...
>>>
>>>Paul T.
>>>
>>>"Bryan" <anonymous@discussions.microsoft.com> wrote in
>> message
>>>news:1e6601c4f6cb$5931dad0$a601280a@phx.gbl...
>>>> The "Wireless UI" does not implement in function
>>>> AdapterIPProperties (\Netui\network.c).
>>>>
>>>> But the CE 5.0 document always says "Implements the IP
>>>> Properties dialog box that is displayed in the network
>>>> connections UI that allows users to configure IP
>>>> addressing, DNS/WINS information, and wireless local
>> area
>>>> network (LAN) settings."
>>>>
>>>> What's the problem?
>>>>
>>>>
>>>> Bryan.
>>>
>>>
>>>.
>>>
>
>



Re: Wireless UI by bryan

bryan
Wed Jan 12 23:50:29 CST 2005

Thanks for your reply.
Do you mean that I have to create an invisible taskbar in
wbtshell?

or Is there a sample code in CE 5.0?

Thanks.


Bryan

>-----Original Message-----
>The easiest solution is to create a "dummy" systray. I
implemented it like
>that (in RDP) and call the WZC configuration dialog
programatically.
>
>Regards,
>
>
>Michel Verhagen
>Windows CE.NET Consultant, eMVP
>PTS Software
>The Netherlands
>
>
>"Paul G. Tobey [eMVP]" <ptobey no spam AT no instrument
no spam DOT com>
>wrote in message news:Oq54%23MB%
23EHA.220@TK2MSFTNGP09.phx.gbl...
>> Yes, that's true and has been reported as a feature
request here
>> previously (or a bug report, maybe, since it used to
do that). One
>> possibility would be to use the API to create your own
WZC interface...
>>
>> Paul T.
>>
>> "Bryan" <anonymous@discussions.microsoft.com> wrote in
message
>> news:162f01c4f7a3$b4b35cc0$a501280a@phx.gbl...
>>> It's right.The Wireless UI is in the folder.
>>> But it is used only for the shell having the systray.
>>> If I use a shell without a systray, the wireless UI
will
>>> not appear. The wireless UI can not receive any
>>> notification without the systray.
>>>
>>> The AdapterIPProperties( ) function does not contain a
>>> wireless sheet any more.
>>> You can compare the function in CE 4.1 and CE 5.0.
>>> The part of wireless was removed.
>>> ..........................
>>> AdapterIPProperties (HWND hWndOwner, LPTSTR
>>> szAdapterName, BOOL fOpenWireless) // CE 4.1
>>> AdapterIPProperties (HWND hWndOwner, LPTSTR
>>> szAdapterName) // CE 5.0
>>>
>>>
>>>
>>>>-----Original Message-----
>>>>I'm not sure I understand what the real question is.
>>> What's the problem or
>>>>what are you trying to accomplish that's related to
>>> this? Yes, the NETUI
>>>>folder contents provides AdapterIPProperties()
>>> implementation. The wireless
>>>>UI stuff is also provided by files in that folder.
>>>>
>>>>If you are complaining about the documentation,
there's
>>> a link, Send
>>>>Feedback, on each help page to report problems with it
>>> to the docs team...
>>>>
>>>>Paul T.
>>>>
>>>>"Bryan" <anonymous@discussions.microsoft.com> wrote in
>>> message
>>>>news:1e6601c4f6cb$5931dad0$a601280a@phx.gbl...
>>>>> The "Wireless UI" does not implement in function
>>>>> AdapterIPProperties (\Netui\network.c).
>>>>>
>>>>> But the CE 5.0 document always says "Implements the
IP
>>>>> Properties dialog box that is displayed in the
network
>>>>> connections UI that allows users to configure IP
>>>>> addressing, DNS/WINS information, and wireless local
>>> area
>>>>> network (LAN) settings."
>>>>>
>>>>> What's the problem?
>>>>>
>>>>>
>>>>> Bryan.
>>>>
>>>>
>>>>.
>>>>
>>
>>
>
>
>.
>