Hi
I have a UltraWinSchedule control and it is working without any issue in Windows 7 machines. However in windows 10 machines we are getting stackoverflow exception. In the call stack I found
Infragistics4.Win.UltraWinSchedule.v11.2.dll!Infragistics.Win.UltraWinSchedule.UltraMonthViewSingleBase.MonthViewSingleAccessibleObjectBase.GetFocused() Unknown
This call is in loop.
Can you please point me in the right direction.
John,
2011 Volume 2 was released before Windows 10 was available so it wasn't tested for use on Windows 10 and it is recommended that you upgrade to a current version of the windows forms toolset if you need to support Windows 10. There were changes to Windows 10 accessibility that could be impacting the issue and it might even be reproducible in Windows 7 using accessibility tools.
Note that we also only support our toolset for three years from release so 2011 Volume 2 is no longer supported. If you are able to provide us a sample that reproduces the exception we will be happy to look at it if it is still reproduced in the latest volume of Ultimate UI for Windows Forms. If it is already addressed there our suggestion will be to upgrade the version that you are using.
If you aren't able to provide a sample and upgrading your application to use the latest volume of Ultimate UI for Windows Forms doesn't resolve the issue, please provide the full call stack that is repeated from the call stack as that might help us identify what might be happening.
Let me know if you have any questions with this matter.
Did you ever solved this problem with the latest released? I have the same issue on some Windows 10 machine but not all of them.
I have been able to avoid this Exception by disabling the AccessibleObject in a subclass of UltraMonthViewSingle.
class UltraMonthViewSingleWithoutAccessibility : Infragistics.Win.UltraWinSchedule.UltraMonthViewSingle { protected override AccessibleObject CreateAccessibilityInstance() { return null; } }
Then, I use this class instead of UltraMonthViewSingle.
Sylvain,
Thank you for posting your workaround.
If you have a sample with steps to reproduce, we could look into the issue further to see if there is something that we should fix in the controls. If you are unable to reproduce it with a sample, the full call stack would allow us to at least review the code involved in the loop to see if we can identify anything obvious.
It would also help to know the exact version that is being used if you don't have a sample that reproduces the issue.
I have this issue only on my PC (running Windows 10), my colleague (also on WIndows 10) has no problems with it. So it seems to be related to some settings in Windows about accessibility but we cannot find it.
The stack trace provided by Visual Studio
System.Windows.Forms.dll!System.Windows.Forms.Control.Focused.get() Unknown Non-user code. Skipped loading symbols.Infragistics2.Win.UltraWinSchedule.v9.2.dll!Infragistics.Win.UltraWinSchedule.UltraMonthViewSingleBase.MonthViewSingleAccessibleObjectBase.GetFocused() Unknown Non-user code. Skipped loading symbols.Infragistics2.Win.UltraWinSchedule.v9.2.dll!Infragistics.Win.UltraWinSchedule.UltraMonthViewSingleBase.MonthViewSingleAccessibleObjectBase.GetFocused() Unknown Non-user code. Skipped loading symbols.Infragistics2.Win.UltraWinSchedule.v9.2.dll!Infragistics.Win.UltraWinSchedule.UltraMonthViewSingleBase.MonthViewSingleAccessibleObjectBase.GetFocused() Unknown Non-user code. Skipped loading symbols.Infragistics2.Win.UltraWinSchedule.v9.2.dll!Infragistics.Win.UltraWinSchedule.UltraMonthViewSingleBase.MonthViewSingleAccessibleObjectBase.GetFocused() Unknown Non-user code. Skipped loading symbols.
...
Infragistics2.Win.UltraWinSchedule.v9.2.dll!Infragistics.Win.UltraWinSchedule.UltraMonthViewSingleBase.MonthViewSingleAccessibleObjectBase.GetFocused() Unknown Non-user code. Skipped loading symbols. Infragistics2.Win.UltraWinSchedule.v9.2.dll!Infragistics.Win.UltraWinSchedule.UltraMonthViewSingleBase.MonthViewSingleAccessibleObjectBase.GetFocused() Unknown Non-user code. Skipped loading symbols. The maximum number of stack frames supported by Visual Studio has been exceeded. Annotated Frame
We are running on v9.2.
Thank you for the call stack. I reviewed the MonthViewSingleAccessibleObjectBase.GetFocused method and found that we did fix this stack overflow in August of 2013. You are correct that it has to do with accessibility and the specific bug that was logged happened when starting the Narrator. As far as what could be different between the two machines, maybe different accessibility features are being used on the two machines. Maybe the Accessibility Tools for Windows page can help you identify what features might be in use that cause this on one machine and not another.
Your best options are to continue to use the workaround that you already are or upgrade to any volume 2013 Volume 2 or newer.