In Windows 11 version 24H2, when using the ExplorerBrowser control's Navigate method to navigate to a search folder (e.g., by calling ExplorerBrowser.Navigate(ShellSearchFolder)), the following issue occurs: If the target search folder is not within the fully indexed scope, or if the system is rebuilding the index, the OnViewEnumerationComplete event of the ExplorerBrowser control is triggered multiple times—once for every batch of loaded data—instead of being triggered only when all file view items are fully loaded.
This behavior causes two major problems. First, it is impossible for users to reliably determine when the file view items have been fully loaded, making it unclear when to perform subsequent operations. Second, attempting to access the ExplorerBrowser.Items property before all file view items are fully loaded leads to UI freezes, severely impacting application performance and user experience.
We urgently request the author to enhance the OnViewEnumerationComplete event of the ExplorerBrowser control to ensure that the event is only triggered after all file view items have been completely loaded. This improvement is critical for resolving the aforementioned issues and significantly improving the usability and reliability of the control. Your assistance is greatly appreciated!
In Windows 11 version 24H2, when using the ExplorerBrowser control's Navigate method to navigate to a search folder (e.g., by calling ExplorerBrowser.Navigate(ShellSearchFolder)), the following issue occurs: If the target search folder is not within the fully indexed scope, or if the system is rebuilding the index, the OnViewEnumerationComplete event of the ExplorerBrowser control is triggered multiple times—once for every batch of loaded data—instead of being triggered only when all file view items are fully loaded.
This behavior causes two major problems. First, it is impossible for users to reliably determine when the file view items have been fully loaded, making it unclear when to perform subsequent operations. Second, attempting to access the ExplorerBrowser.Items property before all file view items are fully loaded leads to UI freezes, severely impacting application performance and user experience.
We urgently request the author to enhance the OnViewEnumerationComplete event of the ExplorerBrowser control to ensure that the event is only triggered after all file view items have been completely loaded. This improvement is critical for resolving the aforementioned issues and significantly improving the usability and reliability of the control. Your assistance is greatly appreciated!