Thanks for supporting map services without feature services in 3.3, I can turn my feature services back off now.
I have an application with many layers and tree-fulls of sub-layers and I've noticed the AttributeTable queries every single sub-layer at startup, regardless of visibility. It only takes 100ms or so, but when you have 500-odd sub-layers... Could it be made smarter so that these queries occur on demand when a layer is enabled?
It may be related, but my Attribute Table is working inconsistently. I can't seem to get it to work right in 3.3. I keep getting one of three scenarios.
1. The Attribute Table works fine and displays all layers, including my excluded layers.
2. The Attribute Table is blank. Opening the Search widget makes it load and then it works correctly.
3. The Attribute Table is always blank.
I'm trying to reproduce each behavior but so far it seems random.
And finally it's impossible to resize the last column if there's a horizontal scrollbar. Columns are sized using the first row's data, so if the last column of the first row happens to be null or something small the whole column is lost. An auto-size option could fix that.
Hope this feedback is helpful.
I have an application with many layers and tree-fulls of sub-layers and I've noticed the AttributeTable queries every single sub-layer at startup, regardless of visibility. It only takes 100ms or so, but when you have 500-odd sub-layers... Could it be made smarter so that these queries occur on demand when a layer is enabled?
It may be related, but my Attribute Table is working inconsistently. I can't seem to get it to work right in 3.3. I keep getting one of three scenarios.
1. The Attribute Table works fine and displays all layers, including my excluded layers.
2. The Attribute Table is blank. Opening the Search widget makes it load and then it works correctly.
3. The Attribute Table is always blank.
I'm trying to reproduce each behavior but so far it seems random.
And finally it's impossible to resize the last column if there's a horizontal scrollbar. Columns are sized using the first row's data, so if the last column of the first row happens to be null or something small the whole column is lost. An auto-size option could fix that.
Hope this feedback is helpful.