Ammar,
Within this list I see a fix for \WinForms\Toolbars\ToolbarsManager with a description of "Maximization problem of the Riboon control on the MDI form". It looks like this issue was fixed within 20083, but not in 20082.
What I am wondering is, what was it that was fixed in that version because I am having an odd issue occur within 20082(2121) where when running on XP SP2 (haven't tested with SP3), if the WindowState is set to Maximized in the designer and the Ribbon control is visible at design time also, that the maximized position of the MDI parent is oddly placed on the screen such that the entire form would be displaced downward about 200 pixels sometimes, and other times just about 50 pixels. This was then hiding the bottom part of the form. Pressing "restore" for the window and then pressing Maximize again would simply place the window at the odd position again. However, having "restored" and then changing the position of the window on the screen and then maximizing would cause it to Maximize to the proper position (to fill the screen). This restore, move, maximize however would only work if the FormDisplayStyle was set to Default (not Standard). Note that this issue only started after moving from 20082.1000 to 20082.2121.
Is this the same issue as was fixed within 20083?
As a follow up, is it perhaps this "fix" that has started causing this issue?
Within UltraToolbarsManager.cs:
Line 32399; private void OnFormHandleCreated( object sender, System.EventArgs e ) {
// MD 9/5/08 - TFS6420 // If the WindowState was set after the handle was created but before we got a chance to synchronize the form border style, the glass in the top dock area was black. // The first place we synced was on the OnFormLoad. Now we will also sync in the OnFormHandleCreated because it doesn't seem to cause any harm.
this.SynchronizeFormBorderStyle( true );
Yes, Bug 10230 was created to fix the issue caused by the fix for Bug 6420. However, it looks like in error it was only fixed in 8.3 and later. This bug should have been fixed in 8.2 as well. I would recommend submitting the issue to the support group and referencing 10230: http://es.infragistics.com/gethelp.
Submitted. Thanks Mike.
I believe it is located within the download.
Thank you for the quick response.
I see the December List, but not January List. Can you please tell me where I can find it? Thanks
Hi,
The “Verified in Version” field is an indicator of what are the versions of NetAdvantage where this bug was verified fix. We usually verify any fix in the version that it was reported in and newer version.For your other question, the latest hot fix for NetAdvantage 8.2 was released in January (build number 8.2.20082.2121) this release should include all bug fixes so far.
I hope this was helpful and thank you for using the forums.Regards,Ammar
I saw the list, and I wondered what the last column (Verified In) mean? Does it mean that the hot fix is applied in these versions, or the issue was also found in these versions?
My firm is currently using 8.2.20082.1000, and I wondered which hot fix is the latest to this release that would contain all the fixes.
Thanks