Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / Windows Forms / Design Time / October 2005

Tip: Looking for answers? Try searching our database.

PRB: .NET Beta2 : Cannot move ContainerControls on designer surface

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Stuart Carnie - 19 Oct 2005 00:42 GMT
I have a working example of a designer host from available working examples

http://www.divil.co.uk/net/articles/designers/hosting.asp

and

http://msdn.microsoft.com/msdnmag/issues/04/12/CustomFormsDesigner/default.aspx

I'd recommend the first link, as it's there appear to be more issues with
the MSDN article example code in v2.0.  The problem is in Beta 2 when
dropping container controls on the designer surface, like a GroupBox or
Panel, these control cannot be moved, as the adornment (the new feature of
Whidbey) is not responding.  A Button or Label can be moved just fine.

I even added the following lines

0001: BehaviorService test =
serviceContainer.GetService(typeof(BehaviorService)) as BehaviorService;
0002: test.BeginDrag += new BehaviorDragDropEventHandler(test_BeginDrag);

after

0001: rootDesigner = (IRootDesigner)host.GetDesigner(form);
0002: view = (Control)rootDesigner.GetView(ViewTechnology.Default);
0003: view.Dock = DockStyle.Fill;
0004: splitContainer1.Panel1.Controls.Add(view);

and receive the Begin Drag events for non-container controls such as Button
and Label, however nothing for the GroupBox or Panel controls.

Any assistance would be appreciated.

Cheers,

Stuart
"Jeffrey Tan[MSFT]" - 19 Oct 2005 03:16 GMT
Hi Stuart,

Thanks for your post.

Yes, I have downloaded the sample project in the first link. I can
reproduce your problem on Whidbey beta2, on the form designer, the
ContainerControl can not be moved.

I am not sure of the root cause for this problem. However I have tested
this issue on the Whidbey release candidate version, the containercontrols
can be moved without any problem. It seems that this problem has been fixed
in Whidbey RC version, so it will be fixed in the release version.

MSDN Subscribers can now download the release candidate of Visual Studio
2005 and Beta 3 of Visual Studio 2005 Team Foundation Server. You can get
it from the link below:
http://lab.msdn.microsoft.com/vs2005/get/default.aspx

Hope this information helps.

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Signature

Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.

Stuart Carnie - 19 Oct 2005 17:20 GMT
Yes it does help, excellent news.  I look forward to RTM.

Thanks for the quick response.

Cheers,

Stuart

> Hi Stuart,
>
[quoted text clipped - 22 lines]
> Get Secure! - www.microsoft.com/security
> This posting is provided "as is" with no warranties and confers no rights.
"Jeffrey Tan[MSFT]" - 20 Oct 2005 04:12 GMT
You are welcome

Best regards,
Jeffrey Tan
Microsoft Online Partner Support
Signature

Get Secure! - www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.


Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.