I have used the below code but its not showing the msgbox. What is wrong with this code ?
Private Sub frmSimple_Disposed(ByVal sender As Object, ByVal e As System.EventArgs) Handles Me.Disposed
Dim result = MsgBox("Are you sure you want to Exit ?", vbYesNo)
If result = DialogResult.Yes Then
me.Close()
End If
End Sub
What is the correct way to handle saving user control settings on form close. I have a tabcontrol that a user can add tabpages during runtime. The user control has a few controls (listbox,combobox,textbox) How can I save the created tabpages and the data in each control in the usercontrol? Below is how I am calling my usercontrol
Code
Public Class TabPageEx
Inherits System.Windows.Forms.TabPage
[code]....
I seem to be a little lost as most documentation seems to suggest that I can not save usercontrol settings in the app.config. I have played around with the solution expl. settings tab without much success. But, then again I may be going about it all wrong. So, I am looking for a little direction on the best way to handle this on form close.
I would like to know the event order of form which is executed while opening form. I am showing my form using following code and the code in form_load event executes twice. Once when the form variables are initialised and second when form is displayed. I want it to execute once only. form showing code:
[Code]...
Do you mean, "opens a file" or "is opened with a file"?
View 1 RepliesI have two forms, "Customer Information Summary" and "Products Sold". They are shown as separate tabs in a MDI window. When the data in "Products Sold" gets updated, I would like an event to fire from that form which could be handled in the "Customer Information Summary" form.
View 1 RepliesBase form baseForm generate an array of childForm (3 fo them). I have one event handler in baseForm which is called when user close each childForm. The problem is that this event handler is only called when the last childForm is closed. When other childForm is closed, the event handler doesn't do anything.
View 7 RepliesI have a VB.NET application writtene using VS 2008 and have been receiving a weird error when a form is closed - it gives me the following error message:
Windows has triggered a breakpoint in MyApplication.exe.
This may be due to a corruption of the heap, which indicates a bug in MyApplication.exe or any of the DLLs it has loaded. This may also be due to the user pressing F12 while MyApplication.exe has focus. The output window may have more diagnostic information.
The immediate window then has this error message:
Critical error detected c0000374
I tried fixing this by just hiding the window, but this simply moves the error up the chain and I get an error when exiting the program as it tries to close the form:
Unhandled exception at 0x7700e29b in MyApplication.exe: 0xC0000005: Access violation writing location 0x00000000.
I don't think I'm doing anything particularly strange in my application - reading from and writing to a database is about as complicated as anything gets for me. I've tried using AppVerifier, but then the program won't even open. I'm at a real loss as I don't know anything about memory management, or what a heap is. I just can't work out why this error is happening
By the way, the application compiles and runs fine on my old 32-bit computer running WinXP professional, but my new 64-bit Windows 7 computer is just not having it, even though I have targeted the compile for x86 and followed every bit of advice I could find on geting it to work in Windows 7. Should Windows 7 and VS 2008 really be incompatible? Do I need to get VS 2010 instead?
I want to execute some code in the MDI Parent Form when an MDI Child Form has been closed. What Parent Form Event would be best.
View 6 RepliesWhat I'm trying to do is your basic "You have made changes... yes/no/cancel" messagebox to show during a form closing event, and when they click cancel to stop the form from actually closing (Whereas yes would save and close, no would just close).
[code]...
I have two forms , first one is search and second is showing the data searched by first form search criteria. When the search query runs it takes lot of sql server resources, so I have passed that query to second form, it searches in database and shows the results. But if the results are not found I wish to close the second form in Form load event. As Second forms form load event searches for the record. I tried to use SecondForm.close in SecondForm.load event but failed to do so.
View 4 Repliesi have a form hold some textboxes ,writed validating-event code and sometime set cancel=true in validatingnow,the problem is,when i click the close button of the form,the validating-event fired,and the form can't close when the validating set cancel=true,but this not i want.i think click "close" that meaning abandon all the form's data,so it not need validate.how can i do ?
View 2 RepliesI have a login form that when the user clicks OK and logs in successfully it loads the main application form.However when I show the main form and close the login form, the app is firing the shutdown event.Is this because the app thinks that the login form is the only form open and thus fires the shutdown event?Here is the code for the login routine, when I call Me.Close() at the end is when the shutdown event is fired. Am I doing things out of order? I used to do it this way in VB6 with no problems (I know they're a lot different).Note, it's nothing in frmMain either, this happens no matter what form I try to open.
Private Sub btnOK_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles btnOK.Click
'iLoginResult = 0 : Success
' 1 : Invalid user name or password
' 2 : Other login error
[code]....
I have a simple Windows Form that hosts property controls at runtime. When the user clicks Close [X] I want to keep the window and its contents alive rather than killing it by handling the FormClosing event, canceling the event and simply hiding the form.
That's fine but at close of the application I need to actually close the window. I implemented the below but it feels kludgey. Is there a simpler, more clever way to handle this situation? (The form's controller calls KillForm explicitly after it receives a closing event from the main window.)[code]...
How to get the handle of a ListBox control in VB.NET 2005?
I am using
Dim i_Handle As ListBox
i_Handle = ListBox1.Handle
But this is not working
Problem that you may have when dealing with two objects that are raising some events. Here, to make it obvious, I am closing the form, but the problem can be experienced with any other 2 classes event. First, what is the problem !
Let suppose that by pressing a button, you want to raise a custom event, then execute a method and then close the form
In that case, you may use a code similar to this
Event BeepIt()
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
RaiseEvent BeepIt()
[CODE]...
There is a panel which contains 2 components: a label and a TreeView. The hierarchy, obviously, looks like this:panel1 // handles Enter event
- label1
- treeView1
I need to do some UI updates when user starts interacting with any of these 3 controls. My attempted strategy was to catch the Enter event of the panel, which would fire when user clicks a label, or TreeView. This way, I can write only one (1) event handler instead of several. While it worked for the TreeView, it didn't work for the label. When I click the label, I don't get the Enter event on the panel. Whats different about the label control? I could handle the Click event of the label. At the same time, I wonder what the other solutions might be.
I have a main form that has a button with which a smaller form is shown. Think of the smaller form as the Find/Replace dialog in many applications, such as Notepad. It's important that the form is (what I believe is called) modal. What I mean is that it always stays on top of the main form. I ensure that by calling the Show method with "Me" as the owner argument. Whenever the small form loses focus it will not disappear into the background but stay visible (albeit out of focus). If you don't understand open up Notepad and have a look at the behavior of the Find/Replace dialog.
Here's my problem: instead of actually closing the form when the X is pressed, I want it to simply Hide itself, so its position and the state of any controls (checkboxes etc) is preserved automatically.To achieve this I simply cancel the FormClosing event and Hide it:
vb.net
Private Sub Form2_FormClosing(ByVal sender As System.Object, ByVal e As System.Windows.Forms.FormClosingEventArgs) Handles MyBase.FormClosing
[code]....
To show the form, I use the following (note the (Me) to make the main form the owner of the form; this ensures that it remains visible even when it is out of focus):
vb.net
Private Sub Button1_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles Button1.Click
Form2.Show(Me)
End Sub
Now. When I run my project, and open the Form2 (small form), then hide it again (by 'closing' it), I can no longer close the main form (Form1)! It seems the main form cannot close when the small form still exists (albeit invisible)...?? When I don't use the Me argument in the Show method, I don't get the behavior I want. I know I can set the TopMost property to True but that will also cause it to become visible on top of all the other forms, even windows not part of my application.
I have a custom control with a bindable property:-
Private _Value As Object
<Bindable(True), ... > _
Public Property Value() As Object
Get
[code]....
Also, here, I'm adding a handler to the DataBindings.CollectionChanged event.This is the second place that I retrieve the type:-
Private Sub DataBindings_CollectionChanged(ByVal sender As Object, ByVal e As System.ComponentModel.CollectionChangeEventArgs)
If e.Action = CollectionChangeAction.Add Then
Dim b As Binding = DirectCast(e.Element, Binding)
[code]....
I need the first place, because the BindingContextChanged event is not fired until some time after InitializeComponent.The second place is needed if the binding field is programatically changed.Am I handling the correct events here, or is there a cleaner way to do it?
Note: My GetValueType method uses the CurrencyManager.GetItemProperties....etc, to retrieve the type.
is it allowed to use more than one Sub to handle the same event ? For example , may I have 2 separate subs to handle the Load event of a form ? Will they fight each other ?I have tested it and it seems to work fine , nevertheless I thought I'd ask you . In case you wonder , there is no great deal , I just want to copy the same lines of code in more forms so I am doing it just in favor of the looking aspect .
View 5 RepliesI have some code in a textbox.Validating event I don't want to execute when the user clicks on the form "X" button to close the form.
View 18 RepliesI am looking to prompt the user to save data when they close a form window in a winforms application. I can't figure out how to trigger the prompt to the user, should they click the red box at the top right corner of the form.
My application currently has a boolean flag, that is set to True on textchanged event. So I will only need to check for the boolean value in whatever event is trigger by the red box.
Whenever I enter text, even a single character, into a textbox in any Form in my application it causes the form and its parent to close. I've checked for the following so far:
Errant/mis-assigned event handlers that may be interpreting a keystroke as a Form cancel I am using keypreview in several windows but debugging shows this to not be a cause Happens in any form of the application Happens even with brand new text boxes dropped on the form Tried removing the WithEvents declaration from text box declarations (VB.NET)
I'm in the process of converting a VB6.0 application to VB.Net (2008 Express). I have a MDI parent form, I'll call mdiBackground, and 4 MDI child forms, frmStatus, frmShow, frmQwerty, and frmSentence.The layout is as follows:mdibackground - has the menus at top and is a container for the child forms.frmSentence - appears at the top frmShow & frmQwerty - appear at the left and when one is closed the other one is in the same position.frmStatus - appears at the right, it has buttons which control when frmShow and frmQwerty are to appear I have a couple of regular forms that act as dialog forms. The Me.Close() works fine on these.
[Code]...
I have set up a notify icon for my form. I want to make it so that when the user clicks the close button that it doesn't close the form it just takes it to shows the notify icon. They can exit the program from the notify icon. Can someone tell me how to keep it running?
View 2 Repliessometimes, when I use Form.close() when debugging my program, although the form is closed, the application is still running. I noticed this behaviour when using the msgbox function.
View 3 Repliesmy web browser is my main form and it has a number of sub forms , how can i set it that when i close the main form my sub forms dont close ?
At the moment when i close the main form all the forms close
I try to transfer a vb6 application to vb2010. In the vb6 I start with a login panel that the user enter uid and password autenticate with the DBServer if ok show application main menu and close the login form. the order of the me.close() after the mainform.show() does not change, The application ends.
View 5 RepliesI have referred DLL in my project. I have to handle the event from DLL in VB.net code. I guess we can do using WithEvents. Can you give me complete picture?
View 2 RepliesI have a situation where me.close() doesn't close the form. I have a form with a button with the code seen below. What happens when the button is clicked is the new form shows, but the original form(calling form) is still there. When I go into debug mode, I can see the me.close() execute, but nothing happens (calling form stays open). When I close the second form both forms close. If I comment out the call for the second form to open the first form closes without problem.
Private Sub cmdNext_Click(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles cmdNext.Click
Dim f As New frmOrder3
[Code].....
[code]But even here it seems the handler isn't registered until after New has completed.However, in real life the event is raised within code that's semantically part of the object initialisation, and I'd really rather not have to create some Initialize function.
View 2 Replies