|
I'm not going to get into this any further because you're beating a dead horse.
But, to add to the description that Ron just posted, in your description, you're ASSUMING that both of your background threads are running at the same time. This is NOT the case! Both threads, MAY be running, or one thread will run and the other won't be, or neither of them will be. Oh, and you're also assuming that threads will run in the order created. None of this is true. Threads can run in any order, for any amount of time, not necessarily the exact same size timeslice.
Normally, the only time you ever look at ThreadState is when you're waiting for it to spin up or waiting for it to end. That's it. Any other use is not reliable as a synchronization method.
|
|
|
|
|
Hi.
I have encountered a peculiar problem with modules that I have never seen before.
Here is a very simple example to demonstrate my point:
Module Module1
Dim x as integer = 1
End Module
Module Module2
Dim y as integer =2
End Module
Private Sub Form_Load(bla, bla, bla)
Me.Text = Str(x+y)
End Sub
When the program runs, both modules are automatically initialized so that the result is the value "3" getting sent to the form.
Up to now, I have never had a problem with modules not getting initialized. But in a new project I am working on, one gets initialized and the other does not. One of them simply does not get recognized. Adding Public to both/either does not help.
Does anyone have an idea as to the kinds of things that can cause this to happen?
Many thanks! 
|
|
|
|
|
treddie wrote: But in a new project I am working on, one gets initialized and the other does not.
Modules are initialized on first use, and the compiler has no incentive to change that behaviour. It should act as a static class does in C#.
treddie wrote: Does anyone have an idea as to the kinds of things that can cause this to happen?
Check your usings; is there any "Module2" in the other namespaces? If there is, then it might be calling the wrong module.
Further, those x and y values should be prefixed with their module-name, to ensure that they're taken from that module (and not some other "global" function called "x").
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
Eddy Vluggen wrote: Check your usings; is there any "Module2" in the other namespaces?
No, no others.
Eddy Vluggen wrote: Modules are initialized on first use, and the compiler has no incentive to change that behaviour.
OK, I think I see what you mean. The form_load procedure is referencing two variables with each declared in each module. Since they are both referenced in the form_load procedure, both modules initialize. But when I change the variable in module2 to "z" instead of "y", there is no reference for it in the form_load, so the compiler deems module2 uneccessary at the present time. At least a test of this confirms it in principle.
Eddy Vluggen wrote: those x and y values should be prefixed with their module-name
That part I knew about...I was just making a very simple demo which was not "safe".
|
|
|
|
|
hi all,
I have a code that get data from database into a datatable. My datatable is bind to datagridview without problem. I challenge is that i want user to perform some conditional formatting like alternate column color, automatically format this datatable adding image header, icon indicators (like what we have in excel). Then user will be allowed to export the datagridview to excel with all formats preserved.
Any help will be appreciated.
Tunde
Tunde
|
|
|
|
|
Member 4624169 wrote: Any help will be appreciated.
There are some articles that show how to format a datagridview. There's probably also some articles on exporting to Excel. Most of them will focus on data - the DGV is exactly that - a gridview. Conditional formatting in a DGV will require code, where Excel will expect markup.
Member 4624169 wrote: Any help will be appreciated.
Anything specific you want to know besides these general pointers?
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
Hi, I need to be able to list all folder, sub folders and files for my application by using a ecurrsive loop how do I do this?
So far I have
Imports System.IO
Partial Class _Default
Inherits System.Web.UI.Page
Protected Sub Page_Load(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Load
If Not IsPostBack Then
Dim AppPath As String = Server.MapPath("~/")
ProcessDirectory(AppPath)
End If
End Sub
Protected Sub ProcessDirectory(ByVal DirPath As String)
Dim Dirs() As String = Directory.GetDirectories(DirPath)
For Each Dir As String In Dirs
Dim tvwRoot As TreeNode = New TreeNode()
If Dir.Substring(Dir.LastIndexOf("\") + 1) <> "App_Code" And Dir.Substring(Dir.LastIndexOf("\") + 1) <> "Bin" And Dir.Substring(Dir.LastIndexOf("\") + 1) <> "Files" Then
tvwRoot.Value = Dir.Substring(Dir.LastIndexOf("\") + 1).ToString
Dim Files() As String = Directory.GetFiles(Dir, "*.aspx")
For Each File As String In Files
Dim tnChild As TreeNode = New TreeNode()
tnChild.Value = File.Substring(File.LastIndexOf("\") + 1).ToString
tvwRoot.ChildNodes.Add(tnChild)
Next
TreeView1.Nodes.Add(tvwRoot)
Dim SubDirs() As String = Directory.GetDirectories(Dir)
For Each SubDir As String In SubDirs
Dim tvwSubFolder As TreeNode = New TreeNode()
tvwSubFolder.Value = SubDir.Substring(SubDir.LastIndexOf("\") + 1)
tvwRoot.ChildNodes.Add(tvwSubFolder)
Dim SubFiles() As String = Directory.GetFiles(Dir, "*.aspx")
For Each File As String In SubFiles
Dim tnChild As TreeNode = New TreeNode()
tnChild.Value = File.Substring(File.LastIndexOf("\") + 1).ToString
tvwSubFolder.ChildNodes.Add(tnChild)
Next
Next
End If
Next
End Sub
|
|
|
|
|
A WinForm-example, you'd have to translate it to a web-environment yourself;
Module Module1
Sub Main()
Using f As New Windows.Forms.Form()
Dim tv As New Windows.Forms.TreeView
tv.Dock = Windows.Forms.DockStyle.Fill
f.Controls.Add(tv)
Dim rootNode As Windows.Forms.TreeNode = tv.Nodes.Add("RootNode")
AddFolder("C:\inetpub\wwwroot", rootNode)
f.ShowDialog()
End Using
End Sub
Sub AddFolder(path As String, parent As Windows.Forms.TreeNode)
For Each folder As String In IO.Directory.GetDirectories(
path, "*.*", IO.SearchOption.TopDirectoryOnly)
Dim folderNode As Windows.Forms.TreeNode = parent.Nodes.Add(
folder, IO.Path.GetFileName(folder))
AddFolder(folder, folderNode)
Next
For Each file As String In IO.Directory.GetFiles(path, "*.*", IO.SearchOption.TopDirectoryOnly)
Dim folderNode As Windows.Forms.TreeNode = parent.Nodes.Add(file, IO.Path.GetFileName(file))
Next
End Sub
End Module
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
|
Uğur Şirin wrote: Can you help me example or source code?
We can help with code if you are stuck or have questions. We do not write code on demand.
Uğur Şirin wrote: I need VB6 Script Codes, use to localhost XP.
VB6 is deprecated; meaning that it's no longer supported.
"Good luck".
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
When a vb6 project is converted to vb.net using visual studio's conversion wizard, all forms and its controls have appearance in that of a vb6. How to change the appearance to vb.net style?
|
|
|
|
|
Rework the form by hand. There is no automated way to do it.
Frankly, you'll probably be rewriting the app from scratch to get all the benefits of .NET.
|
|
|
|
|
Hi.
I think an answer to this problem lies in the use of delegates and marshaling, but if so, I cannot figure this one out.
In vb6, you could use the AddressOf method to get the address of a function. vb.Net no longer allows such a simple idea. Some have even suggested that you do not need to get the address of a function. Apparently they do not use API functions, where getting the address of a function is essential.
Now, in vb.Net, if you attempt to use AddressOf(SomeFunction), as in:
lPrevWndProc = SetWindowLong(hControl, GWL_WNDPROC, AddressOf WindowProc)
You get the following error:
MSDN is as obtuse as ever when describing this problem where a simple example of how to replace the as-simple-as-it-gets vb6 "AddressOf" method with a vb.Net method would have been the obvious thing to do. I reference:
http://msdn.microsoft.com/en-us/library/ms184628%28v=vs.90%29.aspx[^]
which explains no more than the IDE message does in that respect, so they might as well have not even created that link. They offer other links to study which venture off into space because...All they needed to do was offer a simple comparison of how to do in vb.Net, to what was done in vb6.
I have searched high and low for an answer and all I have found is frustration.
Any help would be greatly appreciated. HELP! SOS!
|
|
|
|
|
There is an example here[^] in c#. Just run the code through an online coverter. You may need to touch up a few lines after converting.
|
|
|
|
|
 
Public Class Form1
Public Delegate Function Win32WndProc(ByVal hWnd As IntPtr, _
ByVal Msg As Integer, _
ByVal wParam As Integer, _
ByVal lParam As Integer) As Integer
Private Declare Function SetWindowLong Lib "user32" (ByVal hWnd As IntPtr, _
ByVal nIndex As Integer, _
ByVal newProc As Win32WndProc) _
As IntPtr
Private Declare Function CallWindowProc Lib "user32" (ByVal lpPrevWndFunc As IntPtr, _
ByVal hWnd As IntPtr, _
ByVal Msg As Integer, _
ByVal wParam As Integer, _
ByVal lParam As Integer) _
As Integer
Private Const GWL_WNDPROC As Integer = -4
Private Const WM_LBUTTONDOWN As Integer = 513
Private oldWndProc As IntPtr = IntPtr.Zero
Private newWndProc As Win32WndProc = Nothing
Private Sub SubclassHWnd(ByVal hWnd As IntPtr)
newWndProc = New Win32WndProc(AddressOf MyWndProc)
oldWndProc = SetWindowLong(hWnd, GWL_WNDPROC, newWndProc)
End Sub
Private Function MyWndProc(ByVal hWnd As IntPtr, ByVal Msg As Integer, _
ByVal wParam As Integer, ByVal lParam As Integer) _
As Integer
Select Case (Msg)
Case WM_LBUTTONDOWN
MessageBox.Show("Clicked")
Return 0
End Select
Return CallWindowProc(oldWndProc, hWnd, Msg, wParam, lParam)
End Function
End Class
|
|
|
|
|
What is that you want to accomplish? The code I referenced will work, but is restricted to re-assigning windows owned by the process that invokes it. This is a restriction imposed by the SetWindowLong function (see: http://msdn.microsoft.com/en-us/library/windows/desktop/ms633591%28v=vs.85%29.aspx[^]; for the doc on GWL_WNDPROC).
Here is a version that works for a TextBox on the form.
Imports System.Runtime.InteropServices
Public Class Form1
Private Sub Form1_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.Load
SubclassHWnd(TextBox1.Handle)
End Sub
' Win32 API needed
<DllImport("user32")> _
Private Shared Function SetWindowLong(ByVal hWnd As IntPtr, ByVal nIndex As Integer, ByVal newProc As Win32WndProc) As IntPtr
End Function
<DllImport("user32")> _
Private Shared Function CallWindowProc(ByVal lpPrevWndFunc As IntPtr, ByVal hWnd As IntPtr, ByVal Msg As Integer, ByVal wParam As Integer, ByVal lParam As Integer) As Integer
End Function
' A delegate that matches Win32 WNDPROC:
Private Delegate Function Win32WndProc(ByVal hWnd As IntPtr, ByVal Msg As Integer, ByVal wParam As Integer, ByVal lParam As Integer) As Integer
' from winuser.h:
Private Const GWL_WNDPROC As Integer = -4
Private Const WM_LBUTTONDOWN As Integer = &H201
' program variables
Private oldWndProc As IntPtr = IntPtr.Zero
Private newWndProc As Win32WndProc = Nothing
Private Sub SubclassHWnd(ByVal hWnd As IntPtr)
' hWnd is the window you want to subclass..., create a new
' delegate for the new wndproc
newWndProc = New Win32WndProc(AddressOf MyWndProc)
' subclass
oldWndProc = SetWindowLong(hWnd, GWL_WNDPROC, newWndProc)
End Sub
' this is the new wndproc, just show a messagebox on left button down:
Private Function MyWndProc(ByVal hWnd As IntPtr, ByVal Msg As Integer, ByVal wParam As Integer, ByVal lParam As Integer) As Integer
Select Case Msg
Case WM_LBUTTONDOWN
MessageBox.Show("Clicked")
Return 0
Case Else
Exit Select
End Select
Return CallWindowProc(oldWndProc, hWnd, Msg, wParam, lParam)
End Function
'=======================================================
'Service provided by Telerik (www.telerik.com)
'Conversion powered by NRefactory.
'Twitter: @telerik, @toddanglin
'Facebook: facebook.com/telerik
'=======================================================
End ClassThis is pointless to do as there are other mechanisms to gain access to a textbox's WndProc method. The simplest would be to create custom textbox control and override it's WndProc method.
Public Class mtTB
Inherits TextBox
Private Const WM_LBUTTONDOWN As Integer = &H201
Protected Overrides Sub WndProc(ByRef m As System.Windows.Forms.Message)
MyBase.WndProc(m)
Select Case m.Msg
Case WM_LBUTTONDOWN
' do something
End Select
End Sub
End ClassOr you could create a native window listener as shown here.[^]
|
|
|
|
|
Gawd I'm so stupid sometimes. I was driving home from the store today, and realized I hadn't started the listening process during form load. My version works now...You're version worked perfectly from the get-go.
But furthermore, to get mine to work, I had to change the function declarations to the "other" style.
From:
Private Declare Function SetWindowLong Lib "user32" (ByVal hWnd As IntPtr, _
ByVal nIndex As Integer, _
ByVal newProc As Win32WndProc) As IntPtr
Private Declare Function CallWindowProc Lib "user32" (ByVal lpPrevWndFunc As IntPtr, _
ByVal hWnd As IntPtr, _
ByVal Msg As Integer, _
ByVal wParam As Integer, _
ByVal lParam As Integer) As Integer
To:
<DllImport("user32")> _
Private Shared Function SetWindowLong(ByVal hWnd As IntPtr, _
ByVal nIndex As Integer,
ByVal newProc As Win32WndProc) As IntPtr
End Function
<DllImport("user32")> _
Private Shared Function CallWindowProc(ByVal lpPrevWndFunc As IntPtr, _
ByVal hWnd As IntPtr, _
ByVal Msg As Integer, _
ByVal wParam As Integer, _
ByVal lParam As Integer) As Integer
End Function
Why is one different than the other? I notice that the first is not shared and the second one is.
But I have never encountered any problems before using the first syntax.
modified 2-Jul-13 3:01am.
|
|
|
|
|
When using the "Declare" keyword, the default characterset modifier is ANSI.
From the documentation for Declare[^]
Quote:
Character Sets. You can specify in charsetmodifier how Visual Basic should marshal strings when it calls the external procedure. The Ansi modifier directs Visual Basic to marshal all strings to ANSI values, and the Unicode modifier directs it to marshal all strings to Unicode values. The Auto modifier directs Visual Basic to marshal strings according to .NET Framework rules based on the external reference name, or aliasname if specified. The default value is Ansi.
charsetmodifier also specifies how Visual Basic should look up the external procedure within its external file. Ansi and Unicode both direct Visual Basic to look it up without modifying its name during the search. Auto directs Visual Basic to determine the base character set of the run-time platform and possibly modify the external procedure name, as follows:
On an ANSI platform, such as Windows 95, Windows 98, or Windows Millennium Edition, first look up the external procedure with no name modification. If that fails, append "A" to the end of the external procedure name and look it up again.
On a Unicode platform, such as Windows NT, Windows 2000, or Windows XP, first look up the external procedure with no name modification. If that fails, append "W" to the end of the external procedure name and look it up again.
The error message you should have received was: Unable to find an entry point named 'SetWindowLong' in DLL 'user32.dll'. You could correct this like this:
Private Declare Auto Function SetWindowLong Lib "user32.dll" (ByVal hWnd As IntPtr, _
ByVal nIndex As Int16, _
ByVal newProc As Win32WndProc) As IntPtr
Private Declare Auto Function CallWindowProc Lib "user32" (ByVal lpPrevWndFunc As IntPtr, _
ByVal hWnd As IntPtr, _
ByVal Msg As Integer, _
ByVal wParam As Integer, _
ByVal lParam As Integer) As Integer
|
|
|
|
|
Thanks for the clarification, TnTinMan. Much obliged. So much to learn...So little time!
|
|
|
|
|
|
Thank you, Bernhard!
I am testing it now.
|
|
|
|
|
That is the function, but the problem is the last argument, dwNewLong. In vb6, you could just use AddressOf dwNewLong and the world was happy. But in vb.Net you can't do that because its AddressOf() does not return an address, but a delegate object.
|
|
|
|
|
The AddressOf is fine; it's the P/Invoke declaration which is wrong. You're trying to pass a delegate to a parameter which is declared as taking an IntPtr. In unmanaged code, this would be fine, but in managed code, the parameter types need to match.
To call this method, you would need to declare an overload of the SetWindowLong method with the dwNewLong parameter declared as a WndProc delegate.
However, .NET offers much easier ways to accomplish the same thing. For example, in Windows Forms, you just need to override the WndProc method[^].
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Thanks Richard!
I am trying out all three suggestions to see what happens!
|
|
|
|
|
That's what I couldn't understand, was how to get the address out of the delegate. But one of the things I still get caught up with is that the documented data types for API functions are apparently not sacrosanct. I guess there is some leeway via overloading (which seems hard to find info on in the official sources). In that regard, is overloading the same as subclassing?
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
