|
i am calling showDialog() for form2 from form 1 i want if i close the form2 changes made in form2 appears in form 1 it is fullfillng my requirement for first time but when i call showdialog() 2nd time and malke some chnaging in form 2 it does not appears in form 1....how to solve this problem?
|
|
|
|
|
You haven't provided anywhere near enough information to answer this question. What does your code look like? How are you triggering the update? All this information is needed.
|
|
|
|
|
both forms have text boxes and check boxes data is updated in database and fecthing is from sql qries and set into fom1 textboxes
|
|
|
|
|
And still no code. As it's the code that's wrong, don't you think that you should provide that or are you happy for us to throw random guesses around in the hope that one of them sticks like dung to a wall?
|
|
|
|
|
ShowDialog displays the form and waits for the user to close it with OK or Cancel before it returns. When it does, you can get the changed values from the form instance:
MyForm mf = new myForm();
mf.StringValue = "Hello";
if (mf.ShowDialog() == DialogResult.OK)
{
Console.WriteLine(mf.StringValue);
}
mf.StringValue = "Goodbye";
if (mf.ShowDialog() == DialogResult.OK)
{
Console.WriteLine(mf.StringValue);
}Works fine for me: What are you doing that is different?
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
|
|
|
|
|
Does any one knows : How to drawing text that can rotate in Tao.OpenGL , i search the web for two days already . Can't find some sample like Tao.OpenGl for text . If any one has the samples , please let me know . Thanks very much .
|
|
|
|
|
I never used TAO, however I do know how to use Google[^] and found a couple of relevant articles including this one[^]. I'd say text rotates just like everything else.
|
|
|
|
|
|
It's been a while since I played with the Shell, but I think this is the correct method:
IShellIcon::GetIconOf()
http://msdn.microsoft.com/en-us/library/windows/desktop/bb761275(v=vs.85).aspx[^]
EDIT:
I apologize, I forgot this is the C# forum and answered with a C++ solution. If you know what you're doing, however, you can use the Shell interfaces in C#.
The difficult we do right away...
...the impossible takes slightly longer.
modified 3-Jan-12 23:04pm.
|
|
|
|
|
I want to fill the cells of a datagridview column based on numbers derived at runtime. Sounds easy enough but...
these two lines of code work great if I only wanted red
dataGridView1.Rows[layerCount].Cells[3].Style.BackColor = Color.Red;
dataGridView1.Rows[layerCount].Cells[3].Style.ForeColor = Color.Red;
but these two lines just color the cells text (if existing)? or they just act bizzarly(although they worked good with a listview)
dataGridView1.Rows[layerCount].Cells[3].Style.BackColor = Color.FromArgb(swLayer.Color);
dataGridView1.Rows[layerCount].Cells[3].Style.ForeColor = Color.FromArgb(swLayer.Color);
Anyone have any pointer?
wait a minute, no POINTERS, how about advice 
|
|
|
|
|
My CP Vanity article fills DGV cells with platinum, gold, silver, bronze. No problem, unless the cell is otherwise empty, then it may get tricky.
|
|
|
|
|
what is CP vanity.?? where is code?
|
|
|
|
|
It is one of my articles, as I said. And it has a download link.
|
|
|
|
|
I found an answer.
Using System.Drawing.ColorTranslator.FromWin32()
instead of ArgB();
|
|
|
|
|
I sometimes come across situations where I could use a string type to represent a unique key in something (sorry for being vague)...
An example:
ConnectSensor(new OffScreenSensor(),"screen");
Where the "screen" part is used to identify the OffScreenSensor object in a dictionary somewhere.
I could use an Enum as a replacement but was wondering if any one here has a better way of dealing with stuff like this?
I don't like the idea of having to look back to see the names of keys I have named before 
|
|
|
|
|
strings are fine for identifying, i.e. naming, objects by humans. And I would suggest you store the sensor's name inside the Sensor object, hence turn it into a constructor parameter!
|
|
|
|
|
Ok thanks, sounds like I am on the right track
|
|
|
|
|
Yeah, I would just derive a class from Sensor that manages its own name, something like a GUID for example.
|
|
|
|
|
Names are supposed to be pronounceable, IMO GUIDs aren't.
|
|
|
|
|
True... but why have a pronounceable name for something that doesn't need one?  .
|
|
|
|
|
venomation wrote: if any one here has a better way of dealing with stuff like this?
Depends on the context of 'screen'.
Do you use it as a display name anywhere?
Is it viewable by a user anywhere, like a config value?
Then you need to map to a different value in your code. Mapping of course could still be to a string value. The real issue however is that you want a programmatic value which will not change due to human concerns.
|
|
|
|
|
The idea is that other components can get another component based on its key.
At the moment there is no configuration file aspects, but I may consider it...
The problem is that one type of component can be added multiple times, some of them can be configured to act more generically, in theory I could install two OffScreenSensor's but with different keys.
|
|
|
|
|
That is a different problem however than using a key.
venomation wrote: some of them can be configured to act more generically, in theory I could
install two OffScreenSensor's but with different keys.
Which only apples to what I said if when you say "install" then it refers to something that is basically code, and not something that a 'user' would muck with.
If it does refer to 'code' then you are not using a "component" but rather an instance of a component. So the name refers to an instance even if most only have a single instance.
|
|
|
|
|
Its generally not a good idea to use strings as keys to get components like that. My boss is a notorious mispeller. Do you really want to spend time tracking down why your app doesn't work because somebody spelled it "scren" in 3 out of 100 places? GUIDs as I suggested earlier actually wouldn't be AS prone. Why? I'd probably type in "screen" myself because I can do that faster then copy & pasting from somewhere. With a GUID? I'm not going to type that in. Thats going to be a strict c&p.
Is adding a component multiple times "theoretical"? or is it really going to happen?
Would it be more practical to have a single instance of OffscreenSensor that can sense things from multiple locations?
Instead of doing something like:
Components["Screen1"].EventHappened +=
you could do something like:
IScreenSensor sensor = ServiceLocator.GetService<IScreenSensor>();
sensor.GetScreen(1).EventHappened +=
sensor.GetScreen(2).EventHappened +=
etc.
string keys are also prone to lazy search and replace issues .
|
|
|
|
|
SledgeHammer01 wrote: Its generally not a good idea to use strings as keys to get components like that. My boss is a notorious mispeller. Do you really want to spend time tracking down why your app doesn't work because somebody spelled it "scren" in 3 out of 100 places? GUIDs as I suggested earlier actually wouldn't be AS prone. Why? I'd probably type in "screen" myself because I can do that faster then copy & pasting from somewhere. With a GUID? I'm not going to type that in. Thats going to be a strict c&p.
I would suggest unit testing and system testing to solve that problem. Additionally that also solves the problem where they typed in "alternativeScreen" (a valid component) when it should have been "screen" (also valid.)
And myself I would be opposed to using a guid because that means that to figure out what component instance is in use one would need to look it up every time.
However depending on the actual requirements I would probably use a generated enumeration.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
