Forum Discussion
Sounds like a good suggestion. It might not be the same component type so you might need to look into something else.other than Quantum Grdi but it's worth looking into.
Hi tristaanogre
Actually i tried to do that way but it was not working ,so i tried in different way by digging into the different sections of the object spy where i found this
Aliases.Teachers_debug.wndTfrmMain.dxRibbonBackstageView1.dxRibbonBackstageViewTabSheet1.TLMKTileControl.Items.TileControl.Items.Items[i].TileItem.Text1.Value
Which worked and all the names of the tiles present in the screen was printed in the log message :D .
But the problem was here was the same tile name have two index values like Tile_1 index is 0 as well index 1, Tile_2 index is 3 and as well index 4 ,Tile_3 index is 5 as well index 6 and so on .
In future if i want to click on the tiles also i think we can do it in this was only ,
Does any one have any other better solution than this .kindly let me know
- tristaanogre9 years agoEsteemed Contributor
I wonder if it has to do with tile sizeing? That in that Item list, there are actually two items for each "tile" where one item is a large tile, the other is a small tile, and the visibility is probably the distinguishing factor. Is there any indication of that?