We use cookies to give you the best experience on our website. If you continue to browse, then you agree to our privacy policy and cookie policy.
Unfortunately, activation email could not send to your email. Please try again.

problems with DockingManager in release 4.3.0.31

Thread ID:

Created:

Updated:

Platform:

Replies:

50160 Oct 6,2006 04:13 PM Apr 26,2007 08:40 AM Windows Forms 17
loading
Tags: Tools
Julie Levy
Asked On October 6, 2006 04:13 PM

Since we updated to the latest version, i have noticed some changes with the behavior of our docked tabbed controls. Do you have any documentation on the changes in more detail than the release notes?
Some specific problems: the dock label switches back to the control name in the designer code when you run and autohide the tabbed controls in the EndDockState event. I have attached a sample demonstrating this. See Form3.
I also have a question about getting the size of the controls which are autohidden. The code we were using before is also in Form3. If you hit the button to check the control size when it is docked and when it is autohidden, it is different. Also, when you set the size of the control and then autohide it in the EndDockState event, that size is not used when the control is afterwards docked by the user.
One final issue which i haven''t been able to reproduce in the sample. The EndDockState event is firing 2 times. Previously i was checking the LoadResult property in the event args and only running my code to set the size and autohide properties when it was true. Now LoadResult is always false, never true. What could make LoadResult be false?
Thanks,
Julie

DockedGrids1.zip

Administrator [Syncfusion]
Replied On October 9, 2006 07:06 AM

Hi Julie,

We regret for the inconvenience caused.

-Could you please be more specific on changes with the behavior of docked tabbed controls? so that we could investigate them further and send you a better answer.

-DockLabel issue:This was a known one and we had fixed immediately.

-Getting the size of the controls which are autohidden : We are able to reproduce the issue.It seems we need to calibrate the workaround which used to get the size to consider the height of caption and the Splitter control.
We will be adding a method GetControlSize in our source to resolve the issue.

-Setting the control''s size in AutoHidden mode is not working : It seems the procedure to get the size of control needs to be changed.We will implement the method to get size of control soon and check using that.

-The NewDockStateEndLoad event is firing 2 times :I was not able to reproduce the issue using your sample.Could you please double check your source for additional dockingManager1.LoadDockState() call?
This call will cause the event to fire again.

-LoadResult is always false : This is a known compatibility issue between versions 4.2 & 4.3.We have fixed this issue.Our next patch will contain the fix.

Please let me know,If I missed anything.
Regards,
Joy

Julie Levy
Replied On October 9, 2006 01:42 PM

Joy -
thanks for your quick response. Please let me know as soon as those fixes/additions are in a patch i can download.

As for the DockState stuff. I didn''t put that in the sample yet since it will take a lot of time to reproduce what we are doing in our product. All i know is that it is called twice, i don''t ever make a specific call to LoadDockState or even DockControl (they are docked in the designer), and the LoadResult used be be false then true, but now is false both times. What causes LoadDockState to be called internally? What can cause LoadResult to be false? I''ll see if i can reproduce the behavior in the sample.

Thanks,
Julie

Julie Levy
Replied On October 9, 2006 01:43 PM

Joy -
thanks for your quick response. Please let me know as soon as those fixes/additions are in a patch i can download.

As for the DockState stuff. I didn''t put that in the sample yet since it will take a lot of time to reproduce what we are doing in our product. All i know is that it is called twice, i don''t ever make a specific call to LoadDockState or even DockControl (they are docked in the designer), and the LoadResult used be be false then true, but now is false both times. What causes LoadDockState to be called internally? What can cause LoadResult to be false? I''ll see if i can reproduce the behavior in the sample.

Thanks,
Julie

Julie Levy
Replied On October 18, 2006 04:42 PM

I just heard that there will be a patch next week. Will these docking manager fixes, additions be included in this patch?
Thanks,
Julie

Julie Levy
Replied On October 31, 2006 07:54 PM

I have installed the latest patch (3.4.0.34). Where is the new GetControlSize method?

Thanks,
Julie

Julie Levy
Replied On October 31, 2006 07:59 PM

One more thing: i am still getting the LoadResult always equal to false issue.

Julie Levy
Replied On November 3, 2006 11:14 AM

Is there going to be any response to this thread or should i escalate the issue to an incident?
Thanks,
Julie

Malarvizhi [Syncfusion]
Replied On November 6, 2006 04:03 AM

Hi Julie,

We apology for delay in get back you.

Getting the size of the controls which are autohidden: We increased the priority to fix this issue at the earliest.

LoadResult is always false:The issue is fixed. Currently we are under the testing phase of Docking windows for v.4.4 and these fixes will be included in that version. It will be released probably in this week.We will keep you informed when release is ready.


Regards,
Malarvizhi.

Julie Levy
Replied On November 6, 2006 03:41 PM

thanks for the update.

Julie Levy
Replied On November 21, 2006 06:00 PM

Hi -
4.4 Beta came out today. Did "Getting the size of the controls which are autohidden" make it into the release?
Thanks,
Julie

Malarvizhi [Syncfusion]
Replied On November 22, 2006 05:30 AM

Hi Julie,

The V4.4 Beta doesn't contain the fix for "Getting the size of the controls which are autohidden".Here is the link to track the status of the feature request implementation.
Feature Request #1280 - Need a method to get the size of control when in auto hidden / docked state


We will try to fix this issue at the earliest and keep you informed.

Regards,
Malarvizhi.

Julie Levy
Replied On November 22, 2006 12:18 PM

Thanks for your response.
Any ideas for workarounds (how best to compute the size) until this feature is added?

Also, what about the problem with setting the control's size in AutoHidden mode. Has that been addressed yet?
Thanks,
Julie

Malarvizhi [Syncfusion]
Replied On November 23, 2006 12:48 AM

Hi Julie,

Issue1-Getting the size of the controls which are autohidden

We will try workaround for this issue and keep you informed at the earliest.

Issue2- setting the control's size in AutoHidden mode

We will try to fix this issue at the earliest and keep you informed.


Thanks for using the Syncfusion product,

Regards,
Malarvizhi.

Administrator [Syncfusion]
Replied On December 19, 2006 03:56 PM

Any update?
Thanks,
Julie

Murugan [Syncfusion]
Replied On December 19, 2006 06:48 PM

Hi Julie,

We really regret for the inconvenience caused. We are currently working on these issues with high priority. We will fix the issue soon and keep you informed.

Regards,
Murugan P.S

Julie Levy
Replied On April 24, 2007 06:49 PM

Hi -
Last i heard this was being worked on. Any update on whether it will be in the new release?
Thanks,
Julie

Poly J [Syncfusion]
Replied On April 26, 2007 08:40 AM

Hi Julie,

We are very much sorry for the delay in providing the fix for the issue you have reported. Could you please create a Direct-trac incident with subject line "Issue with setting the size in autohide mode - F50160 ". We will send you the bug fix details through our direct trac system.

Regarding the Feature Request #1280 [Need a method to get the size of the control when in auto hidden / docked state.], we have not included this in 5.1 version. I have increased the priority of this and forwarded this to our development team.

Best Regards,
Poly

CONFIRMATION

This post will be permanently deleted. Are you sure you want to continue?

Sorry, An error occured while processing your request. Please try again later.

You are using an outdated version of Internet Explorer that may not display all features of this and other websites. Upgrade to Internet Explorer 8 or newer for a better experience.

;