|
Hi David,
I didn't use databinding, so defining the datasource should be good enough... and it also works for showing the data for the first time. Maybe I have to check out the databinding approach, but that has other pitfalls with my approx. 25 columns. Still thank you.
EDIT: I tried the approach using the collection as the datasource of a BindingSource. While the collection as well as the BindingSource are filled properly, the DGV still doesn't update.
|
|
|
|
|
Michael Schäuble wrote: While the collection as well as the BindingSource are filled properly, the DGV still doesn't update.
Easiest way to bind a collection to a grid, is a BindingList[^]. I'm often populating it with objects that implement the INotifyPropertyChanged interface; AFAIK, that's the easiest route.
Bastard Programmer from Hell
if you can't read my code, try converting it here[^]
|
|
|
|
|
Second that I use it and it works well! +5
Lobster Thermidor aux crevettes with a Mornay sauce, served in a Provençale manner with shallots and aubergines, garnished with truffle pate, brandy and a fried egg on top and Spam - Monty Python Spam Sketch
|
|
|
|
|
Thank you, Eddy - with a BindingList it seems to work!
|
|
|
|
|
This may be a very novice question. If so, sorry for that, but the solution is just not coming to me.
I have a form1 with a button and a datagrid in it. When I press the button I have to open another form2 which will accept some information, and then come back to form1 and use information provided by form1 to filter the data in the datagrid in Form1.
My problem is if I give Form2.show in the button click event then the control completely passes to form2 and returning to form1 button.click event is becoming difficult for further processing.
I want to keep the form2 separate since I will be using the same process to filter data in another form3.
Can anyone help me in solving this issue.
|
|
|
|
|
Use the ShowDialog() [^] method, which treats the form as a popup dialog.
One of these days I'm going to think of a really clever signature.
|
|
|
|
|
Thanks a lot Richard.
It helped
|
|
|
|
|
Dim cAutoit As New AutoItX3Lib.AutoItX3
cAutoit.Send("{DOWN}")
System.Threading.Thread.Sleep(150)
cAutoit.Send("{ENTER}")
Using this code on a hotkey, I'm trying to make the hotkey navigate the halo trial menu to start a server.
The problem is that no natter how I adjust the pause it is always incomplete, (It will skip keypress, or do nothing all together.)
I need it to press: "down, enter, down, down, down, down, Enter" consistently without fail can someone PLEASE help me?
|
|
|
|
|
Here at CP? Probably not.
But, at the AutoIt forums, here[^], yes, they probably could.
|
|
|
|
|
|
Hi
Is there any software using VB on Production Planning for Manufacturing Company with Source Code.
Thanks
|
|
|
|
|
Quite possibly; a Google search would give you some answers.
One of these days I'm going to think of a really clever signature.
|
|
|
|
|
Google It...
Tarun Mangukiya
|
|
|
|
|
Jagjit Saini wrote: Is there any software using VB on Production Planning for Manufacturing Company with Source Code
Yes
Why is common sense not common?
Never argue with an idiot. They will drag you down to their level where they are an expert.
Sometimes it takes a lot of work to be lazy
Please stand in front of my pistol, smile and wait for the flash - JSOP 2012
|
|
|
|
|
I have an MDI Parent with menu strip. There are two MDI Child forms. I want the first MDI Child to fill the parent for which I have used the Dockstyle.Fill which is working fine. But the second child form I want it to be Center screen and have set the Start Position in the properties. But when I open the second child first time from the menu it fills up the Parent. If I close it and open again then it shows center screen. Can anybody help me to solve this problem?
|
|
|
|
|
Set the WindowState of the first MDI-child to Maximized, would work better ith Windows - the docking works better if you're dealing with controls inside a panel-control. Once that is fixed, the other Window will no longer be confused by the Docked Window.
Make sure the second window is neither docked, nor maximised.
Bastard Programmer from Hell
if you can't read my code, try converting it here[^]
|
|
|
|
|
Thanks a lot Eddy.
It actually started working after removing the Dockstyle property.
Thanks again
|
|
|
|
|
Great, glad it worked
Bastard Programmer from Hell
if you can't read my code, try converting it here[^]
|
|
|
|
|
It is a known problem with MDI.
if the first window is set with either dock or windowstate all subsequent windows will inherit that setting.
The only way I have around it I have found is to either change these settings before opening the second window or to set the size of the first window manually, i.e. Form1.size = new size(100,100) where you would replace the "100" with the actual size that you want etc.
Lobster Thermidor aux crevettes with a Mornay sauce, served in a Provençale manner with shallots and aubergines, garnished with truffle pate, brandy and a fried egg on top and Spam - Monty Python Spam Sketch
|
|
|
|
|
Yes Simon, You are absolutely right. It worked once the Doskstyle settings were removed.
Thanks for the explanation.
|
|
|
|
|
your welcome
Lobster Thermidor aux crevettes with a Mornay sauce, served in a Provençale manner with shallots and aubergines, garnished with truffle pate, brandy and a fried egg on top and Spam - Monty Python Spam Sketch
|
|
|
|
|
It's not really a "known problem", but is, in fact, the expected behavior.
Too many people use MDI without knowing what it's really designed to do. The vast majority of those people don't even need to use MDI.
|
|
|
|
|
How do I to change the cursor for a left-mouse-button drag initiated from the shell (not the form)?
I don't want to use the standard vb.net cursor, I'd like to use a custom cursor and even better, use the cursor that the shell is using before it hits my form.
Can you point me in the right direction please
Mark
|
|
|
|
|
Well, it's possible to override the default cursors you see during a drag'n'drop operation, but it's not pretty.
See this series of articles on MSDN[^]. Yeah, it's so complicated that it's covered by a series of articles!
It's not that bad really, depending on your skill level of course.
|
|
|
|
|
Thanks Dave! I did read through that article and boy, you're right. The amount of code it takes to duplicate the behavior of the shell is more then the syntax check parser I've been writing.
I'm thinking out loud here but I wonder if I could simply trap the cursor through the message pump instead. I would still need to create a custom cursor and deal with the int24 already being captured by the left mouse button press but maybe I wouldn't have to write a novella to produce the same results
Mark
|
|
|
|