I guess I asked for it!! But as there's no use of docking or anchoring in the example, I guess I don't know what wouldn't work right if those were set.
If the issue isn't "dock and anchor aren't sufficient" but rather "we can't / won't spend time setting the dock and anchor properties correctly on all those forms" then what you should be trying to build (IMO) is not your own dynamic layout manager. You should instead build a more static tool that can set the dock and anchor properties appropriately. At 01:06 AM 9/2/2004, Ranjan wrote >I can post some initialize component code here[1], no problem with that. We >are using Infragistics components. And unfortunately by the time I joined >the team, every form was in a proper working condition, except for the fact >that no anchoring, no docking had been done and the UI design on the >client's part was complete. I tried Xsizer[0]. Ofcourse it didn't work. It >works good enough for small applications, and even the C-One suggested did. >But for ours, no chance. Its so random Havent tried the layout manager, but >I guess its very late. I think I will have to write my own resizing >component. Custom to my application. And yes, when you look at the code, you >will know why it's a big effort. >I will check the autolayout manager. I think its going to be very useful. >Thanks for all the help. Enjoy reading VS.Net generated code. >[0] www.xsizer.com >[1] Don't kill me. This is really horrible, but somebody asked for it (no >rant at J.Merril) >private void InitializeComponent() [snip!!!!] J. Merrill / Analytical Software Corp =================================== This list is hosted by DevelopMentor� http://www.develop.com Some .NET courses you may be interested in: Essential .NET: building applications and components with CSharp August 30 - September 3, in Los Angeles http://www.develop.com/courses/edotnet View archives and manage your subscription(s) at http://discuss.develop.com
