Problem with AutoHidePortion in DockPanel Suite 2.8.0 (VB2010)
-
A docking pane is set to AutoHidePortion and permitted docking is DockLeft with AllowEndUserDocking = False The design width of the form is 200px and the initialisation command is .Show(dockPanel, DockState.DockLeftAutoHide) Despite the fact that AutoHidePortion is > 1 the pane is showing at around 315px = 1/4 the form width. I have just moved from DPS ver 2.5 to ver 2.8 and in ver 2.5 this behaviour is not apparent and the form (pane) displays at the required size. I an using VB 2010. Does anyone have any further information on this, workarounds or fixes? I can't seem to find anything specific on the web, or in Code Project. Thanks.
-
A docking pane is set to AutoHidePortion and permitted docking is DockLeft with AllowEndUserDocking = False The design width of the form is 200px and the initialisation command is .Show(dockPanel, DockState.DockLeftAutoHide) Despite the fact that AutoHidePortion is > 1 the pane is showing at around 315px = 1/4 the form width. I have just moved from DPS ver 2.5 to ver 2.8 and in ver 2.5 this behaviour is not apparent and the form (pane) displays at the required size. I an using VB 2010. Does anyone have any further information on this, workarounds or fixes? I can't seem to find anything specific on the web, or in Code Project. Thanks.
TheComputerMan wrote:
I can't seem to find anything specific on the web, or in Code Project.
That's probably because it is not part of the .NET Framework. Are you referring to this[^] suite? If yes, then your question should go here[^].
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]
-
TheComputerMan wrote:
I can't seem to find anything specific on the web, or in Code Project.
That's probably because it is not part of the .NET Framework. Are you referring to this[^] suite? If yes, then your question should go here[^].
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]
It is implemented in Visual Basic therefore the question is legitimate. I will ask in the suggested forum however although I have already searched that and found nothing specific.
-
It is implemented in Visual Basic therefore the question is legitimate. I will ask in the suggested forum however although I have already searched that and found nothing specific.
TheComputerMan wrote:
It is implemented in Visual Basic therefore the question is legitimate.
I never said it wasn't.
TheComputerMan wrote:
I will ask in the suggested forum however although I have already searched that and found nothing specific.
I doubt that there'll be specific information readily available. The reason I pointed there is because a support forum dedicated to that suite will probably have more expertise than a general .NET forum.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]
-
TheComputerMan wrote:
It is implemented in Visual Basic therefore the question is legitimate.
I never said it wasn't.
TheComputerMan wrote:
I will ask in the suggested forum however although I have already searched that and found nothing specific.
I doubt that there'll be specific information readily available. The reason I pointed there is because a support forum dedicated to that suite will probably have more expertise than a general .NET forum.
Bastard Programmer from Hell :suss: If you can't read my code, try converting it here[^]
It's OK I understand what you were saying, but I was thinking that maybe people ding the job had come across the problem and fixed it or got a workaround. Unfortunately there is nothing much about it on that site. The problem gets a mention. Apparently it appeared in 2.6 and has not been fixed satisfactorily as far as I can tell. The forum is a bit 'thin' to say the least. In the end, because the code has to address .NET 4.0 I simply re-compiled version 2.5 to target the .NET 4.0 framework. Since the problem does not exist in 2.5 I am happy and I am not concerned about the additions in later versions that i will not have by using 2.5. At least if someone else experiences the problem our discussion is here to give them a pointer. Thanks for your input. :thumbsup:
-
It's OK I understand what you were saying, but I was thinking that maybe people ding the job had come across the problem and fixed it or got a workaround. Unfortunately there is nothing much about it on that site. The problem gets a mention. Apparently it appeared in 2.6 and has not been fixed satisfactorily as far as I can tell. The forum is a bit 'thin' to say the least. In the end, because the code has to address .NET 4.0 I simply re-compiled version 2.5 to target the .NET 4.0 framework. Since the problem does not exist in 2.5 I am happy and I am not concerned about the additions in later versions that i will not have by using 2.5. At least if someone else experiences the problem our discussion is here to give them a pointer. Thanks for your input. :thumbsup: