C# Discussion Boards - CodeProject

How to add a form in a dockpanel

4-Jan-07 0:49

I assume of course that in cbo2 you give the DisplayMember a different value, right? Try to make a break point to see if this value applies or not.
Anyway, I've been working with ADO .Net and databindings for quite a while now, and let me tell you I'm completely displeased with it. It has many bugs, and what would Microsoft would call "features" that costed me a lot of time to discover it. When I submitted somehting to them all they said was "Make your own workaround. We don't have the time to fix this in the next version of Visual Studio. Thank you!", and that's it.
Anyway. A good way -that works for me- is to use a BindingSource and bind it to your controls using cbo1.DataBindings.Add() method. It works fine fr the Text property -but not with CheckBox.Checked property BTW-. A sample would be

BindingSource UsersSource = new BindingSource();
UsersSource.DataSource = dsUsers.Tables["Users"];
cbo1.DataBindings.Add(new Binding("SelectedItem", UsersSource, "Name"));
cbo1.DataBindings.Add(new Binding("SelectedValue", UsersSource, "UseID"));

I hope it works for you! Smile | :)

-- modified at 6:55 Thursday 4th January, 2007

The above code I use for a DropDownList combobox. You can also bind to the Text property according to your need.

Regards

GunaChinna3-Jan-07 22:51

GunaChinna

3-Jan-07 22:51

Hi there,
Can you please tell me, how can i add a form in a dockpanel in c# 2005.

Pete O'Hanlon3-Jan-07 23:16

Pete O'Hanlon

3-Jan-07 23:16

You can't add a form. What you can do is add a user control.

the last thing I want to see is some pasty-faced geek with skin so pale that it's almost translucent trying to bump parts with a partner - John Simmons / outlaw programmer

Deja View - the feeling that you've seen this post before.

GunaChinna4-Jan-07 0:56

GunaChinna

4-Jan-07 0:56

Thanks. Why i want to add form in a dockpanel means, i want to create my dockpanel to contain controls like, toolbox, properties window, output window as they are dockable and hidable, closeable. So.. is there any way to achieve this environment?

Sk8tz4-Jan-07 1:21

Sk8tz

4-Jan-07 1:21

I had the same prob..

A work around I used was, Do a normal form, then when you happy, happy with it, change inheritance to usercontrol. And that does the trick.

Unfortunately you have the uglyness of have to change the inheritance back to a form when you have to modify it.

Hope this helps

Sk8tZ

How to store a "VARIANT" varible via .NET ?

Robert Rohde4-Jan-07 2:59

Robert Rohde

4-Jan-07 2:59

Hi,

set the TopLevel property of your Form to false before trying to add it.

Robert

Clark Nu China3-Jan-07 22:43

Clark Nu China

3-Jan-07 22:43

Now I'm working on a project written by C#, we have an ActiveX compment include in our UI for get and display data from a fingerprint device.
The Activex gives data in "VARIANT" type, by default it will be mapped to "object" type in C#, and now I want to store it into database, and restore it and pass it back to the ActiveX compment to use.
Currently I'm using the simple way of serialize support of .NET platform, but I'm not sure whether it works since I have no test data yet. (the device was broken and sent for repair). In fact I don't think .NET is so smart.
Anyway, if it does work, how can I get my purpose? All I want is to convert the data into something can be stored into database(sqlserver) and restore it from database.

Clark Nu

Re: How to store a "VARIANT" varible via .NET ?

Ed.Poore3-Jan-07 22:47

Ed.Poore

3-Jan-07 22:47

I thought there was a "variant" (or is it binary?) type in (I presume you're using SQL) the database. If you just persist the object from C# into the database and reload it it'll come back as an object. The object can then be sent to the ActiveX.

I have no idea what I just said. But my intentions were sincere.

Taking Snap-Shots... HOW???

tario3-Jan-07 22:09

tario

3-Jan-07 22:09

hi all,
i'm trying to create a windows service that takes a snap-shots every single time unit..
Is there any Class or Method in C# to take a snap-shots from the desktop or the monitor??
Thanks

TaRiQ

Martin#3-Jan-07 22:19

3-Jan-07 22:19

Hello,

You have to use "gdi32.dll" methods.

        using System.Runtime.InteropServices;

[DllImport("gdi32.dll", SetLastError=true)]
private static extern int BitBlt(IntPtr hdcDest, int nXDest, int nYDest,
    int nWidth, int nHeight, IntPtr hdcSrc, int nXSrc, int nYSrc,
    int dwRop);

[DllImport("gdi32.dll", SetLastError=true)]
private static extern IntPtr CreateDC(string lpszDriver, string lpszDevice,
    string lpszOutput, IntPtr lpInitData);

private static int SRCCOPY = 0x00CC0020;

public static Bitmap Screenshot()
{
    Graphics formGraphics = YoureForm.CreateGraphics();
    Bitmap bitmap = new Bitmap(YoureForm.ClientRectangle.Width, YoureForm.ClientRectangle.Height, formGraphics);
    Graphics bitmapGraphics = Graphics.FromImage(bitmap);

    IntPtr formDC = formGraphics.GetHdc();
    IntPtr bitmapDC = bitmapGraphics.GetHdc();

    if (BitBlt(bitmapDC, 0, 0, YoureForm.ClientRectangle.Width,
        YoureForm.ClientRectangle.Height, formDC, 0, 0, SRCCOPY) == 0)
    {
        formGraphics.ReleaseHdc(formDC);
        bitmapGraphics.ReleaseHdc(bitmapDC);
        throw new Exception("API-Error" + Marshal.GetLastWin32Error() +
            " BitBlt");
    }
    formGraphics.ReleaseHdc(formDC);
    bitmapGraphics.ReleaseHdc(bitmapDC);
    return bitmap;
}

Hope that helps!

All the best,

Martin

Nader Elshehabi4-Jan-07 0:16

4-Jan-07 0:16

Instead of API, you can use Graphics.CopyFromScreen() method.

Regards

Martin#4-Jan-07 0:33

4-Jan-07 0:33

Hello,

Nader Elshehabi wrote:
you can use Graphics.CopyFromScreen() method.

Not with .Net1.1

Nader Elshehabi4-Jan-07 0:53

4-Jan-07 0:53

Come on man! DotNet 3.0 is on the market. You should upgrade!!

If you use C# Express edition -which I believe got DotNet 1.1 only-, you can still use features from DotNet 2.0 using a trick I made sometime ago. Simply:
1- Install DotNet 2.0 on your machine and include it in the minimum requirement in your doumentation.
2- Add a reference in your project. Select browse
3- Browse to the DotNet 2.0 folder -I believe it was under "Windows\System32" folder-, and explicitly reference the Assembly you want. In our example it should be "System.Drawing.Dll" file.

Regards

DavidNohejl4-Jan-07 1:21

DavidNohejl

4-Jan-07 1:21

Nader Elshehabi wrote:
Come on man! DotNet 3.0 is on the market. You should upgrade!!

Are you telling this to your customers? WTF | :WTF:

"Throughout human history, we have been dependent on machines to survive. Fate, it seems, is not without a sense of irony. " - Morpheus

Nader Elshehabi4-Jan-07 1:35

4-Jan-07 1:35

I thought Martin was one of our boys! Laugh | :laugh:

Regards

DavidNohejl4-Jan-07 1:58

DavidNohejl

4-Jan-07 1:58

Yeah, but the fact that there is .NET Framework 3.0 doesn't mean that all .NET 1.x project will suddenly move to new platform - ultimately, this decision is up to customer (guess who pays you...) and try to explain them you must move project to newest version of .NET in order to take snap-shot. Good luck with that. Smile | :)

"Throughout human history, we have been dependent on machines to survive. Fate, it seems, is not without a sense of irony. " - Morpheus

Nader Elshehabi4-Jan-07 3:04

4-Jan-07 3:04

Easy with the flames partner!! Big Grin | :-D

DotNet 2.0 is already everywhere. I always release my software to that platform, and non of my customers ever complained Smile | :)

. You don't upgrade to take a snap shot. I upgrade because I should upgrade. They didn't release new versions for you to watch them and say "Ummm.. What about my customers?".
I'm not mocking you. Seriously. I'm stressing the point that we should let go of DotNet 1.1. You'll be limiting yourself too much. There are many features in 2.0 that could cut your workload to half. If you don't use them already then you got no problem -just one big question mark-. Many large software already states DotNet 2.0 as a minimum requirement. You don't get any Windows xp now without DotNet 2.0 integerated. Besides, if you still target users who don't have DotNet 2.0, just ship it with you CD or give them the link to download it free!!
DotNet 3.0 was just an example. I don't release my software for that platform yet. All I'm talking about is why do I still hear people asking for backward compatibility with DotNet 1.1?? Why not 1.0 then? Smile | :)

Do you still use Windows Me ot 98?
Bottom line:
With all do respect to you -seriously again-... Move forward.

Regards

DavidNohejl4-Jan-07 3:48

DavidNohejl

4-Jan-07 3:48

Nader Elshehabi wrote:
Easy with the flames partner!!

What flames? I was merely stating a fact.

Nader Elshehabi wrote:
I always release my software to that platform, and non of my customers ever complained. You don't upgrade to take a snap shot. I upgrade because I should upgrade.

I understand you, but you are forgetting that Martin is probably NOT creating new software in .NET 1.x, but rather modifying/fixing/adding functionality to some older application written in .NET1.x. If that's large codebase, all tested and proved to work in production environment, why would you migrate it to .NET 2.0? Don't fix it when it's not broken. Do you think that when .NET came C++ applications should've been rewritten into .NET just because it's there and it's cooler? That's just insane. OK, I hear ya. .NET 2.0 is backward compatible. But not 100%. And installing anythin new on server (let alone .NET framwork) is always security risk. Plus all that time spent cost money as well.

My point is that benefits of newer version of .NET are obvious when creating NEW software (or rewrite, major upgrade), but that doesn't mean that all code written in previous version suddenly disappeared.

Nader Elshehabi wrote:
With all do respect to you -seriously again-... Move forward.

FYI I am developing web applications in ASP.NET 2.0

"Throughout human history, we have been dependent on machines to survive. Fate, it seems, is not without a sense of irony. " - Morpheus

Daniel Grunwald4-Jan-07 1:31

Daniel Grunwald

4-Jan-07 1:31

C# Express supports .NET 2.0 only. There is no way to make it use another runtime by choosing specific .dlls.
Note that .NET 3.0 uses the same runtime as .NET 2.0, so you can use .NET 3.0 libraries with C# Express.

Nader Elshehabi4-Jan-07 1:37

4-Jan-07 1:37

Daniel Grunwald wrote:
C# Express supports .NET 2.0 only

Never worked with it! It was just a guess. If so then why Martin was worried about .Net 1.1??

Regards

Martin#4-Jan-07 2:01

4-Jan-07 2:01

If I would program just for fun, I would upgrade every single day!

But as somebody said before, there are allways customers involved!
So I have to stay with .Net1.1 as long as the new generation of our product is coming. (Problem is that generation 1 isn't ready yet)

All the best,

Martin

Nader Elshehabi4-Jan-07 3:11

4-Jan-07 3:11

You give your customer the minimum requirements. Otherwise games would have suck with DirectX 7 or 8, or even earlier. Video cards would have frozen in the earlier technologies, etc...
Got my point?? If you still prefer API, go ahead. But don't blame me if you fall behind your schedule.

Regards

Martin#4-Jan-07 4:09