What is to gain by using the OpenNetCF Notification control over the MS version?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Earl - 24 Apr 2006 17:01 GMT

I am so frustrated with Microsoft's notification control that I am ready to
explode. I can make it function perfectly within a single form, but moving
between forms and from a message stream (i.e., like a viable app might
actually have to do) has created some issues that make it seem like the
control is just a toy, usable only within the form where it is created (*end
vent*).

My question is as the subject says: will I gain any functionality by going
to the OpenNetCF control?

Reply to this Message

Peter Foot [MVP] - 24 Apr 2006 17:33 GMT

The OpenNETCF version works in the same way, it was written to provide much
the same functionality but under .NETCF v1.0. It misses a few features such
as Icon support due to limitations in the v1.0 framework, the control is
omitted from the SDF v2.0 as it doesn't add anything to the standard
Microsoft one in .NETCF v2.0

When you create a Notification object you should store a reference to it
somewhere globally in your app, as it doesn't belong to a specific form.
Depending on what you use the control for you can either reuse a single
Notification object and change it's contents and status or raise multiple
notifications for different events.

Peter

Signature

Peter Foot
Windows Embedded MVP
www.peterfoot.net | www.inthehand.com

>I am so frustrated with Microsoft's notification control that I am ready to
>explode. I can make it function perfectly within a single form, but moving
[quoted text clipped - 5 lines]
> My question is as the subject says: will I gain any functionality by going
> to the OpenNetCF control?

Reply to this Message

Earl - 24 Apr 2006 17:57 GMT

Thanks Peter. I have indeed tested a global notification object, and have
been getting the same respone -- the control activates, shows the incoming
message, does not give me an error with or without Invoke, does not freeze
on the call to the control, but hangs when I click on a button or link. The
HTML within the control has been reviewed, modified, and tested, and it is
correct, but this is wacky.

Alas, I will need an icon for this project, so that is not the direction I
can go. It is also a 2.0 project.

> The OpenNETCF version works in the same way, it was written to provide
> much the same functionality but under .NETCF v1.0. It misses a few
[quoted text clipped - 19 lines]
>> My question is as the subject says: will I gain any functionality by
>> going to the OpenNetCF control?

Reply to this Message

Thomas Hall - 25 Apr 2006 15:39 GMT

Peter,

I'm using SDF 1.4 on PPC 2003 (WinCE 4.2) -- is the Dipose method of
the OpenNETCF.WindowsCE.Forms.Notification object supposed to
acknowledge (and therefore remove) the notification from the system
notification area?

Regards,
Thomas

Reply to this Message

What is to gain by using the OpenNetCF Notification control over the MS version?

Free Magazines