|
|
Fixed in build 5.0.4.2652 BTW: As a workaround there is 'viewchange' method that can be listened on document.body, usage e.g. in filterEditor.js, searchBar.js etc. image.png (12,335 bytes) |
|
|
I am not sure that listening on 'viewchange' on document.body is the best way since it could fire for so many reasons. I am currently trying to use: app.listen(window.currentTabControl.multiviewControl.mainControl.controlClass.dataSource, 'change' ... and: app.listen(window.currentTabControl.mediatree.controlClass.dataSource, 'change' ... but neither is perfect. I am waiting to see how your fix is applied and if it is better. |
|
|
Listening 'viewchange' on document.body is better way as in MM5 the nodes can be navigated even if the Media tree is disabled (e.g. via breadcrumbs or via node grids) and 'viewchange' will always fire. My fix in 2652 was just adding the Promise (as return value of all navigationHandlers) |
|
|
This doesn't work always, tried with dbFolder. I copied your window.navigationHandlers.dbFolder.navigate function to my script, added true as the second resolveWhenFinished argument to navigateNodePath(nodePath), and now it works fine. By the way, it would be nice if you modify this particular navigate method to conditionally accept the first argument (path) as a string. I could continue using my modification of that method, but it would be better if you do that in the built-in script. |
|
|
Implementation verified 2667 @Ludek please close/triage after reviewing @Zvezdan question at 0019162:0068642 |
|
|
Fixed in 2668 |
|
|
Verified 2670 |
- Anonymous
