BuyLog In
Bug Report T353138
Visible to All Users

The IndexOutOfRange exception is raised while restoring a default state for recurring exceptions

created 9 years ago

Before upgrade when you change one recurrence appointment it work perfectly to restore the default state, now after the upgrade to 15.2 if i move one recurrence appointment when click on restore default state raise me an error…
what else change there?
im receiving an error in this method, nothing changes, i open my last version now and it works perfect.

Appoiment[] updateAppoiments = SchedulerExtension.GetAppointmentsToUpdate<Appoiment>("scheduler", lst, lst, ResidentSchedulerHelper.DefaultAppStorage(), ResidentSchedulerHelper.CreateDefaultResourceStorage());

index out of range, what change there? because is the same code.,…

Thanks

Show previous comments (3)
DevExpress Support Team 9 years ago

    Hello Sergio,
    It is difficult to provide any estimate in such cases. Usually our R&D team researches issues quickly. However, sometimes even a simple issue has a very complex cause and cannot be solved soon. Therefore, I cannot say precisely when this issue will be researched, but I assure you that our developers do their best to find the cause as soon as possible.
    We will keep you informed of our progress.

    SC SC
    Sergio Cabrera 1 9 years ago

      ok Oleg thanks. maybe in the meantime we can hide that option to the menu. Would you mind telling me if I can hide this option restore default state from the menu.

      Thanks

      DevExpress Support Team 9 years ago

        To remove this item from the "Appointment" context menu, handle the SchedulerSettings.PopupMenuShowing event as shown below:

        C#
        SchedulerSettings settings = new SchedulerSettings();  
settings.Name = "scheduler";  

settings.PopupMenuShowing = (send, evargs) => {  
    MVCxScheduler scheduler = send as MVCxScheduler;  
    if(evargs.Menu.MenuId == SchedulerMenuItemId.AppointmentMenu) {  
        evargs.Menu.Items.Remove(evargs.Menu.Items.FindByName("RestoreOccurrence"));  
    }  
};
        Sign in to comment on this post

        Answers approved by DevExpress Support

        created 9 years ago

        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.

          Sign in to comment on this post

          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.