When in weeks view with several weeks selected - if I click above the scroll thumb indicator it takes me back 3 months at a time instead of just one. Clicking below will take me one month as expected. XE2 project attached. I believe it should scroll back or forward the same number of weeks that are currently displayed.
cxDateNavigator - The date navigator skips months and does not maintain the number of selected weeks when an end-user moves selection either by pressing the Page Up/Page Down key or clicking the scheduling area scrollbar shaft
Answers approved by DevExpress Support
We have fixed the issue described in this ticket and will include the fix in our next maintenance update. To apply this solution before the official update, request a hotfix by clicking the corresponding link for product versions you require.
Note: Hotfixes may be unavailable for beta versions and updates that are about to be released.
Hello,
Thank you for your message. I am afraid that I was not able to compile your project. The *.pas file is missing in the attached archive. Would you please provide us with a full source of your demo?
In addition, I suggest you update the version of our controls to the latest one (VCL 12.2.3). The issue may be solved there.
I simply put a scheduler component on a form, nothing else. Make sure you have about four weeks selected in the date navigator. I use the component in another program and do not have this issue, but I can't find any code preventing it. There must be some combination of property settings that cause it.
Please provide me with a small sample project to precisely replicate your scenario on our side.
attached
Just run the executable - you should see a month (weeks) view in the cal component. Click above the thumb scroll indicator. It will take you back in three month increments while clicking below does as expected taking you forward in one month increments. The up scroller is going in larger increments "out of the box" and I can't figure out why.
Hello,
Thank you for your detailed report. I have reproduced the described behavior and forwarded this ticket to our developers for research.