[DevExpress Support Team: CLONED FROM T641520: Switching the current time zone using the OptionsView.CurrentTimeZone property doesn't reposition events]
Hi Paulo,
This problem is still there in 18.2. Can you fix it permanently?
Best Regards
[DevExpress Support Team: CLONED FROM T641520: Switching the current time zone using the OptionsView.CurrentTimeZone property doesn't reposition events]
Hi Paulo,
This problem is still there in 18.2. Can you fix it permanently?
Best Regards
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.
Disclaimer: The information provided on DevExpress.com and affiliated web properties (including the DevExpress Support Center) is provided "as is" without warranty of any kind. Developer Express Inc disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
Confidential Information: Developer Express Inc does not wish to receive, will not act to procure, nor will it solicit, confidential or proprietary materials and information from you through the DevExpress Support Center or its web properties. Any and all materials or information divulged during chats, email communications, online discussions, Support Center tickets, or made available to Developer Express Inc in any manner will be deemed NOT to be confidential by Developer Express Inc. Please refer to the DevExpress.com Website Terms of Use for more information in this regard.
Thanks. I have reproduced this problem. It seems that this time it is caused by different code. It may take us some time to examine it.
Hey Paulo,
Any news on the problem? I need to deploy program soon.
Best Regards
Hello,
To my regret we do not have a solution yet. It will take us some more time to resolve this issue.