Posted 16 years ago
by Mike Turner
Version: 4.5.0484
Platform: .NET 3.5
Environment: Windows XP (32-bit)
We've been noticing an issue where the expander (customize QAT button) does not always redraw properly. We've seen this under two situations:
1. Several buttons are added to the QAT and the application window is resized (expand / shrink the app width a bit). When we do this using a modified version of the ribbon sample, the expander disappears (we can also do this with the unmodified sample). We can force it to redraw by shrinking the app width all the way and then expanding it.
2. The QAT starts with just a few buttons but several are added (3 or 4) via the customize menu. As buttons are added, at some point the customize QAT button (down arrow) becomes the expander (>> button) and cannot be clicked. As above, we can force the button to redraw by shrinking the width of the application and stretching it back out. At that point, the expander can be clicked again.
Unfortunately (or fortunately :-) ), #2 above may be reproduced reliably in our application, but we haven't been able to duplicate it using the ribbon sample. At this point in development, we have four ribbon tabs and a single context tab. The QAT starts with 3 buttons with options to add 4 more (for a total of seven).
1. Several buttons are added to the QAT and the application window is resized (expand / shrink the app width a bit). When we do this using a modified version of the ribbon sample, the expander disappears (we can also do this with the unmodified sample). We can force it to redraw by shrinking the app width all the way and then expanding it.
2. The QAT starts with just a few buttons but several are added (3 or 4) via the customize menu. As buttons are added, at some point the customize QAT button (down arrow) becomes the expander (>> button) and cannot be clicked. As above, we can force the button to redraw by shrinking the width of the application and stretching it back out. At that point, the expander can be clicked again.
Unfortunately (or fortunately :-) ), #2 above may be reproduced reliably in our application, but we haven't been able to duplicate it using the ribbon sample. At this point in development, we have four ribbon tabs and a single context tab. The QAT starts with 3 buttons with options to add 4 more (for a total of seven).
