dtpick.Format=8
dtpick.CustomFormat="MMM dd, yyyy HH:mm:ss (tt) zzz"
I'm afraid that is .NET/OS issue I can do nothing about.1. The input object is not VGA-aware (cosmetic issue)
I copied the Custom Date Format part of the help from my ControlExDesktop help and that in turn I got from the .NET DateTime object custom formatting help. It looks like the DateTimePicker control, for some reason, only implements a sub-set of the formats available. The good news is that, although undocumented, the B4PPC DateFormat() & TimeFormat() functions support most of those formats including time zone (on the desktop at least, I haven't tried the device) because they both use a .NET DateTime object. Actually they are really the same function and both return identical results when given the same format strings. DateFormat() is not restricted to date formats and TimeFormat() is not restricted to time formats! Have a play2. Can't get the time zone displayed
Yes, I was going to polish the library a bit so I will add this.Is is possible to add Screen.Width and Screen.Height returning the
dimensions of the physical screen, irrespective of form dims and optimized
or legacy compiled applications? The idea is to query the device for VGA
or QVGA displays.
To be pedantic they are the screen dimensions but it is the size of the virtual screen that is being drawn on rather than the physical size that is being returned. I haven't yet found a way to get that.Display.width and height return the form dimensions, not the screen's.
Thanks for pointing that out. I had written them correctly in the Help source but a quirk of the Help Compiler resulted in the same text being shown for two different topics - now corrected in the zip.BTW, the help file topics Display and Status Bar have the same contents.
Have you poked around HKEY_LOCAL_MACHINE\Drivers\ Display\... The names of the entries may be manufacturer/software driver specific but you are looking for something like "CxScreen" and "CyScreen". They might be virtual or physical sizes - I don't know and don't have access to a vga device to find out.Probably, this information is stored in the registry in device vendor specific locations.
From the .NET documentationThe image tag <img src...> is supported but won't display any image.
I chickened out of mentioning the HTML bit in the Help in case it opened a bag of worms in support terms as my knowledge of HTML is c***pThe text can be plain text or HTML. The Pocket PC HTML control renders the HTML to be the best of its ability. The following elements are unsupported and ignored:
BGSOUND tag
images
meta tags
script
If anyone understands what that means and thinks it is useful I can implement the event and provide the response string.In addition to plain text, you can create a user notification with HTML content in the message balloon. The HTML is rendered by the Pocket PC HTML control, and you can respond to values in an HTML form by parsing a response string provided by the ResponseSubmittedEventArgs class, through the Response property.
Cmd:2 Identifier
The identifier "cmd:2" has a special purpose in Windows CE and is used to dismiss notifications. If cmd:2 is the name of an HTML button or other element in a message balloon, the ResponseSubmitted event is not raised. The notification is dismissed, but its icon is placed on the title bar to be responded to at a later time.
I quoted from the docs that came with Visual Studio 2005 but this link http://msdn2.microsoft.com/en-us/library/microsoft.windowsce.forms.notification.aspx seems identical.Can you please unveil the link which leads to the .NET documentation you have quoted? )
Yes, I use ControlsExDevice library. Thank you, this is exactly, what I needYou should use the version in my ControlsExDevice library http://www.b4x.com/forum/additional-libraries/1995-controlsexdevice-library.html There is a bug with events in the original version
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?
We use cookies and similar technologies for the following purposes:
Do you accept cookies and these technologies?