isolate window ids via markup init (as opposed to js init)

Webix JS
#1

neither of the below markup config for isolate is working

    <div webix-ui view="window" position="center" modal="true" move="true" height="670" width="900" 
webix-ready="notificacionPreviewWindowReady(root)">
        <config name="isolate" value="true"></config>
OR
        <config isolate="true"></config>

I am getting ‘root.$$ is not a function’ on notificacionPreviewWindowReady

Basically what I am trying to achieve is the markup equivalent of

$scope.config = {
        isolate:true,
...
};
#2

You can subclass the window widget to add the isolate property to it. The protoUI command can be used to create a new ui type, which will be accessible both from a config and from a markup

webix.protoUI({
  name:"iwin"
}, webix.ui.window, webix.IdSpace);
...
<div webix-ui view="iwin" position="center"

http://webix.com/snippet/496e5f0b

Missing “isolate” on a window is a miss from our side, so it will be added in 4.1

#3

Works for a window, does not work for a layout

window - http://webix.com/snippet/ef4fd961 - works

layout - http://webix.com/snippet/ed03fd2b - container.$$(‘subjectText’) undefined

#4

Sorry, was a mistake in my snippet, change order of extending to

webix.protoUI({
  name:"iwin"
}, webix.IdSpace, webix.ui.window);
#5

unfortunately ilayout breaks my datatable pager - switch between layout and ilayout view type to see the effect
http://webix.com/snippet/a13e6074 - how should I specify the pager in isolated mode?

webix.js:547 Uncaught TypeError: Cannot read property ‘$view’ of undefined(…)pager_setter @ webix.js:547(anonymous function) @ webix.js:546(anonymous function) @ webix.js:17

#6

also iwin causes richselect data not to show (it does if I revert back to win)

<div view="richselect" id="combo" webix-data="data" 
webix-ready="comboReady(root)"></div>

and comboReady is not being called - is this expected behaviour?

#7

webix-ready will be processed only for the same element which has webix-ui directive ( top level webix control )

#8

As for error, it is a known issue, where pager can’t be located by its ID if pager is inside of isolated view. Will be fixed in the next update.

#9

much appreciated, not sure if you have confirmed the issue with the richSelect as well, will try and provide a snippet for that. Also could not find any release schedule info, do you have an estimate for your next release?