Visual Basic

Re: How to launch application from Microsoft.WindowsCE.Forms.MessageWindow

11-Apr-13 2:54

Hello,
I created an application for Windows CE 5.0 in VB. The class application AppCEClass is inherited from Microsoft.WindowsCE.Forms.MessageWindow. I have a problem to launch an application, because something like this does not work:

Public Shared Sub Main()
Application.Run(New AppCEClass())
End Sub

Windows does not recognize the class name and throw error AppCEClass() cannot be converted on System.Windows.Forms.Form.

What to do?

modified 11-Apr-13 9:22am.

Richard MacCutchan11-Apr-13 6:05

Richard MacCutchan

11-Apr-13 6:05

I think your application should inherit from System.Windows.Forms.Form.

Use the best guess

Re: How to launch application from Microsoft.WindowsCE.Forms.MessageWindow

dusty_dex11-Apr-13 6:30

Re: How to launch application from Microsoft.WindowsCE.Forms.MessageWindow

11-Apr-13 6:30

yes, that's what I was trying to get across in the other thread by providing an example.

Re-WndProc-does-not-work-in-Windows-CE-5-0.aspx

"It's true that hard work never killed anyone. But I figure, why take the chance." - Ronald Reagan

That's what machines are for.

Got a problem?
Sleep on it.

Richard MacCutchan11-Apr-13 21:35

Richard MacCutchan

11-Apr-13 21:35

I often wonder why some questioners make life so difficult for themselves, and go round and round in circle rather than accepting advice or guidance.

Use the best guess

Re: How to launch application from Microsoft.WindowsCE.Forms.MessageWindow

dusty_dex11-Apr-13 22:40

onMouseDownClickcount () event handler usage

11-Apr-13 22:40

> "I often wonder why some questioners make life so difficult for themselves, and go round and round in circle rather than accepting advice or guidance." <

Yes, it's like they're blinded by their own self belief that they are right, can't see at all. Even when they patently don't have a deep understanding of coding and won't admit it.

There's not much point continuing to help them, so I send them elsewhere. Big Grin | :-D

"It's true that hard work never killed anyone. But I figure, why take the chance." - Ronald Reagan

That's what machines are for.

Got a problem?
Sleep on it.

econy10-Apr-13 15:18

Re: onMouseDownClickcount () event handler usage

10-Apr-13 15:18

I looked the following code in MSDN, but don't know how to test it. is onMouseDownClickcount() an event handler? then how can I link it to a control, ex: button?

The following example creates a MouseButtonEventHandler which determines if a single, double, or triple click occurred. ClickCount property is used to determine the number clicks.

private void OnMouseDownClickCount(object sender, 
MouseButtonEventArgs e)
{
    // Checks the number of clicks.
    if (e.ClickCount == 1)
    {
        // Single Click occurred.
        lblClickCount.Content = "Single Click";
    }
    if (e.ClickCount == 2)
    {
        // Double Click occurred.
        lblClickCount.Content = "Double Click";
    }
    if (e.ClickCount > 3)
    {
        // Triple Click occurred.
        lblClickCount.Content = "Triple Click";
    }
}

Bernhard Hiller10-Apr-13 22:18

Bernhard Hiller

10-Apr-13 22:18

You found that here[^], didn't you? You ought to tell us the source.
It looks like an event handler for mouse events in a WPF application. Hence you cannot use it in a Windows Forms application.

Re: onMouseDownClickcount () event handler usage

econy11-Apr-13 7:27

WndProc does not work in Windows CE 5.0

11-Apr-13 7:27

yes, I found the code in MSDN website.

Member 989133410-Apr-13 3:05

10-Apr-13 3:05

Hello,
I am doing program in VB for Windows CE 5.0. I need to catch messages from other programs in VB window. In VB is defined a function WndProc. But, this function does not work (or exist) on CE. Compiler cannot recognize it.

Protected Overrides Sub WndProc(ByRef recWinMessage As Microsoft.WindowsCE.Forms.Message)
    MyBase.WndProc(recWinMessage)
End Sub

Can anyone help me?

dusty_dex10-Apr-13 4:26

10-Apr-13 4:26

You might be able to implement missing features using Library imports + P/Invoke

Look toward the end of this article. msdn.microsoft.com/en-us/library/aa446564.aspx

"It's true that hard work never killed anyone. But I figure, why take the chance." - Ronald Reagan

That's what machines are for.

Got a problem?
Sleep on it.

Member 989133410-Apr-13 22:52

10-Apr-13 22:52

I tried to read an article, but I didn't find anything helpful. Problem is, that I am using VB for Windows CE and there is not supported WndProc. What can I do?

This is a fragment of code. What I am doing wrong? WndProc cannot be recognized od VB for Window CE.

<dllimport("coredll.dll", setlasterror:="True," charset:="CharSet.Auto)"> Private Shared Function FindWindow(ByVal lpClassName As String, ByVal lpWindowName As String) As IntPtr
End Function

<dllimport("coredll.dll", setlasterror:="True," charset:="CharSet.Auto)"> Private Shared Function SendMessage( _
ByVal hwnd As IntPtr, ByVal wMsg As Int32, ByVal wParam As Int32, ByVal lParam As Int32) As Int32
End Function
<dllimport("coredll.dll", setlasterror:="True)"> _
Private Shared Function SetWindowLong(ByVal hWnd As IntPtr, ByVal nIndex As Integer, ByVal dwNewLong As WndProc) As Integer
End Function

Public Shared Sub Main2()
Dim ip As IntPtr
ip = FindWindow(vbNullString, "Kvant 1.0")
If (ip <> 0) Then
MsgBox("Kuk!")
SendMessage(ip, &H10, 0, 0)
End If
End Sub

Dim GWL_WNDPROC As Long = -4
Dim lpPrevWndProc As Integer

Public Function SubClass(ByVal lHwnd As Long) As Boolean
Beep()
lpPrevWndProc = SetWindowLong(lHwnd, GWL_WNDPROC, AddressOf WndProc)
End Function

Protected Overrides Sub WndProc(ByRef recWinMessage As Microsoft.WindowsCE.Forms.Message)
MyBase.WndProc(recWinMessage)
End Sub

Shared Sub Main()
Application.Run(New AOutForm())
End Sub

dusty_dex11-Apr-13 0:42

11-Apr-13 0:42

Did you add the reference to Microsoft.WindowsCE.Forms in your project?

It is supported.

"It's true that hard work never killed anyone. But I figure, why take the chance." - Ronald Reagan

That's what machines are for.

Got a problem?
Sleep on it.

Member 989133411-Apr-13 2:31

11-Apr-13 2:31

Yes. When I inherit class like this

Partial Public Class AOutForm
Inherits Microsoft.WindowsCE.Forms.MessageWindow

then WndProc works, but I have problem to launch application, because

Application.Run(New AOutForm())

does not work. What to do?

dusty_dex11-Apr-13 3:05

11-Apr-13 3:05

The VB My feature is supported in the compact framework. Perhaps that will simplify your efforts

msdn.microsoft.com/en-US/library/5btzf5yk(v=vs.80).aspx

I can't find any useful info about Application.Run with the current MSDN site. Dead | X|

So I keep having to switch to another machine that has most of the old Windows CE stuff.

Can you let me know any error codes that you receive, I will be able to look those up, on the other machine too.

Smile | :)

"It's true that hard work never killed anyone. But I figure, why take the chance." - Ronald Reagan

That's what machines are for.

Got a problem?
Sleep on it.

Member 989133411-Apr-13 3:31

11-Apr-13 3:31

How can I create a dialog Window in VB for CE. I mean something like DoModal() in C++. Sorry, I have just poor knowledge about this.

The error message what you are asking me for is:

Error 3 Value of type 'AOut.WNDMSG' cannot be converted to 'System.Windows.Forms.Form'. C:\Program Files\Measurement Computing\DAQFlex for Windows CE\Examples\VB\AOut\AOutForm.Common.vb 209 25 AOut

dusty_dex11-Apr-13 3:42

11-Apr-13 3:42

Let's see if this helps.

microsoft.windowsce.forms.messagewindow%28v=vs.80%29.aspx

"It's true that hard work never killed anyone. But I figure, why take the chance." - Ronald Reagan

That's what machines are for.

Got a problem?
Sleep on it.

Member 989133411-Apr-13 3:49

11-Apr-13 3:49

I know that example. I does not help me because my Window class is derived from Microsoft.WindowsCE.Forms.MessageWindow, not from System.Windows.Forms.Form.

dusty_dex11-Apr-13 4:09

11-Apr-13 4:09

You might get more help within Microsoft's own developer forums, as there's scant info about Windows CE programming on the wider web.

They have been happy to help me in the past.

"It's true that hard work never killed anyone. But I figure, why take the chance." - Ronald Reagan

That's what machines are for.

Got a problem?
Sleep on it.

Member 989133411-Apr-13 4:15

11-Apr-13 4:15

Do you have a web address?

dusty_dex11-Apr-13 4:55

SaveFileDialog.ShowDialog() return value

11-Apr-13 4:55

Start here: Smile | :)

social.msdn.microsoft.com/Forums/en-US/category/smartdevicedevelopment

"It's true that hard work never killed anyone. But I figure, why take the chance." - Ronald Reagan

That's what machines are for.

Got a problem?
Sleep on it.

econy9-Apr-13 9:06

Re: SaveFileDialog.ShowDialog() return value

9-Apr-13 9:06

I use the statements like the following:

If SaveFileDialog1.ShowDialog() = System.Windows.Forms.DialogResult.OK Then
               If SaveFileDialog1.FileName = "" Then
                   MsgBox("Plase input file name ")

Then if I don't input file name in the dialog,just press the save button, it seems the dialog can't return, i.e, close it.

Is the DialogResult.OK requires user must input filename?

Eddy Vluggen9-Apr-13 9:36

Eddy Vluggen

9-Apr-13 9:36

The "ShowDialog" method is blocking; it will halt the execution of the current thread until the dialog is dismissed by the user. You're checking whether the result of that method equals the enumerated value "DialogResult.OK".

Bastard Programmer from Hell Suspicious | :suss:

If you can't read my code, try converting it here[^]

Re: SaveFileDialog.ShowDialog() return value

econy9-Apr-13 9:39