Have you seen the Graphics[^] class? If you handle the OnPaint event of a control you can use it to draw anything you want on it. :badger:

Pity :( It's a MDI application, user can even move the MDI forms around and align them parallely to work together. Now I have many troubles synchronize them. Anyway, thanks for you answers, I can use them in some other cases.

The reason I have to change the graphics' PageUnit to inch because I want all to draw in inch measurement. If you test you code above, you will see that it draws a dotted line with 1 inch width. So you need to convert 1 inch width pen to 1 pixel with pen with PixelToInch method above. I hope you can understand my explanation because English is not native language. Thank you.

You would do better to ask this on the CC.NET mailing list. There aren't any public discussion forums for CC.NET, but the mailing list is very active and generally responsive. One option is to create 3 separate CC.NET build projects and then link them together with project triggers. Scott Dorman Microsoft® MVP - Visual C# | MCPD President - Tampa Bay IASA [Blog][Articles][Forum Guidelines] Hey, hey, hey. Don't be mean. We don't have to be mean because, remember, no matter where you go, there you are. - Buckaroo Banzai

Yes, its fast drawing, but not as fast as Word does. I just use and old-fashion double-buffer drawing techique. For object moving, I use GDI rubberband line and curve to draw. It not good for now, fast on drawing rectangle, but for ellipse, I have to flatten the graphics path, so it's extremly slow when drawing moving ellipse. I will show you the code (or even send mail to you all the source code) the next Monday, because I don't bring code to home and today is Saturday :D Anyway, do you interest of building a canvas component that can draw and transform shapes, group shapes, support zooming, ect or know any body experienced about this?...... I'm stuck on this now because I working alone :((

Hello, I think the "DefaultValue" Attribute is what you are looking for. If it's equal to the designtime setting, it will not generate code for this property. Be aware that the property has to be initialized correct. Hope it helps! All the best, Martin

You can use memprofiler (mentioned in the other post) and you can also use the CLR Profiler[^] tool. You really shouldn't be calling GC.Collect() yourself in any case. All this does is force a garbage collection cycle to run "out of turn", which ultimately causes more work for the GC. Whenever a collection cycle runs, your applications main thread is frozen for the duration of the cycle...so the more times you force a collection, the worse your performance will become. Once you close the form, are you setting the variable reference to null? ----------------------------- In just two days, tomorrow will be yesterday.

I disagree, it is not just good practice. Calling Dispose on instances of a class that has a Dispose() method is mandatory; the class may or may not hold unmanaged resources (encapsulation makes that knowledge irrelevant), and Dispose() would take care of them. So there are two basic rules: - if you design a class that holds unmanaged resources, you MUST provide a Dispose() method - if a class offers a Dispose() method, you MUST call it when (or as soon as) you are done with its instance(s). Hope this helps. Luc Pattyn [My Articles]

I got the problem when using Graphics object to draw text, like this Graphics g; g.DrawString("Text", font, brush, rect, format); with format is an instance of System.Drawing.StringFormat No way to strect the text lines to have the same width :(( Thanks for your answer anyway.

Help help help! After searching the internet, I found nothing :(

Yes, I have checked it, the method is "IsVisible". Thx a lot.

I tried it too, I override the IsInputKey method for the FORM, and the method was not called. According to MSDN, it should be called.....

I agree with Chris. I've dealt with C++ projects where the developer went crazy with typedefs. Even though C# has a similar ability, it is much simpler to use the native data type names. They may not be as short as we want or as clear within the specific application domain, but they are unambigous and standard. I don't have to worry about a new developer trying to understand what an IntStringPair is, or look for it on MSDN. KeyValuePair clearly defines the object using terms that everyone is familar with. ----------------------------- In just two days, tomorrow will be yesterday.

You can add the assembly to the GAC[^] (Global Assembly Cache). That way, the clients of the library can all share the same assembly, instead of each one having a copy in its application directory. Have a look at gacutil[^], which is a utility in the SDK that allows you to add/remove assemblies from the GAC. Regards Senthil _____________________________ My Blog | My Articles | WinMacro

Go to Project Properties ---> General--->Supported runtimes -->give ur Version 2.0 or 1.1 "Every morning I check Forbes 40 richest Indians list , if i'm not there I go to work."

Nam, You can put the partial class in code-behind in your custom namespace as you would with the ASP.NET 1.1: namespace MyNameSpace { public partial class Class1 : System.Web.UI.Page { .... } } And you will do this in the code editor, also remember to update the Inherits attribute accordingly: <%@ Page Language="C#" AutoEventWireup="true" CodeFile="..." Inherits="MyNameSpace.Class1" %> So basically, you would not need to worry about the code to declare all the server controls placed in the web page .aspx since they are placed in another dynamic partial class generated by the ASP.NET. The idea behind this is to seperate all automatically generated code in a partial class so that the code in your code-behind is really neat and clean, and you can freely access the controls in code-behind. Duong Tien Nam wrote: I dont think that abandoning the namespace in the code-behind file is a good idea Unfortunately, I haven't seen a way using the IDE to set the namespace for the partial class by default, that means you would need to use the code edtior. And I guess that you might find it difficult or strange to you, but in fact, there are some big changes in the ASP.NET compiling model over the ASP.NET 1.1. In old version of the ASP.NET, you basically have a single output assembly whose name is normally the namespace declared in code-behind. At runtime, this assembly is put in the bind folder, and with this model you will have some disadvantages like updating the assembly. However, you should be much more flexible with the new compiling model introduced in the ASP.NET 2.0. You can find more information from the links: ASP.NET Compilation Overview [^] ASP.NET Web Page Code Model [^] http://weblogs.asp.net/scottgu/archive/2005/08/21/423201.aspx[^] You can certainly find more re

I am using 2.0. If you are using 1.1, try the following although I have not tried this: IntPtr hWnd = //your handle from CreateWindow Control control = new Control(); Type type = typeof(Control); FieldInfo field = type.GetField("window", BindingFlags.Instance | BindingFlags.NonPublic); Type windowType = typeof(NativeWindow); NativeWindow window = (NativeWindow)field.GetValue(control); MethodInfo method = windowType.GetMethod("AssignHandle", BindingFlags.Instance | BindingFlags.NonPublic); method.Invoke(window, new object[] {hWnd, false}); {parent form/control}.Controls.Add(control);