Answere inline:
Yes it does seem a bit dim
absolutely - and this is not the only one... i'm hardly "impressed" about
the limited BASIC-functions of such a modern concept.
Unfortunately this removing functionality is crippling
and having to resort to PInvoke raises portability issues.
yes. And even if you don't use PInvokes, you will get applications which
are working different.
Take the "DateTimeEdit" for example. This is a windows-common-control for
years (if not decades) but not available in .Net (yes - now there's one
available from MS - but it is a good example). Now what happens?
One developer will use a standard Edit and use Convert to get a date.
An other will code it's own Date-Edit with a popup-calender
An other will code it's own Date-Edit with a better Popup-Calender but
without Time-Edit
etc.
now the client will install 2 .Net applications and has to use TRHEE
different styles to enter a Date:
1. in PocketOutlook and EVERY OTHER native PocketPC Application
2. two (or more) different styles in .Net Apps
I don't think that this is the modern way of building applications. And the
client will not understand nor accept this, because the PocketPC device is
then switched from a smart device to a complex device where you have to
think bevor entering data...
I personally draw several lines around my centre line to make it thicker
Well this may work in some cases - i will try this too. The Problem: it is
getting slower with each line.
do you have problems with gaps between some lines if you draw a thicker
line? And how to make sure that it is always - for example - 5 pixels wide?
(in every angle)
How do you do you capture and redraw - mine seems a bit clunky and the
writing is a bit angular - I may have to resort
to splines to get a smoother image.
splines would be nice - havn't looked if they are available in .NET :-( ...
and: when using splines - how to draw them 2 or 4 pixels wide?
currently i'm using a PaintBox to capture MouseDown/-Move/-Up events. In
these events i save the mouse-position and draw lines between the last and
the current position (and a single Pixel in the MouseDown event to be able
to draw single taps as points)
This works good on my ipaq2210 but of course could be faster and better (i
really like to have antialiasing and such things. So i really think about
switching to GAPI or something (i think i've read something about a .Net
wrapper for it)
Maybe a new version of the framework will have this functionality but I
wouldn't expect it soon.
i really don't expect this in near future because this would destroy the
whole concept. Think what would happen:
- there are devices with .Net Version 1 build in
- You are developing for Version 2
- Now what happens? The client cannot simple download and use your
application! Either you have to deploy the whole Version 2 of .Net (big
download) or the client has to search (and know!) him/herself where to get
the new CF and how to install it - and it will consume rare memory of the
device...
- and as far as i understand it should be compatible to Version 1 - but
will it really? This is a risk of the client he propably likes to be
aware... and then switches to an other product (not .Net?) which works good
and maybe has the same features
I really have mixed emotions about .Net (especially the CF)... it's nice to
code and you can reuse code for the desktop. The software is running on
PocketPC2002 and 2003 (and 2000 too i think) and CE4 devices ....
But as soon as you have to use PInvokes to get the features you need it may
be the better way to use eVB or eVC directly :-( (both i find horroble ;-)
)
Boris