Forum Discussion

subbu_valliappa's avatar
subbu_valliappa
Contributor
9 years ago
Solved

Close DotNetBar TabStrip/TabItem

I'm testing on DevComponents.DotNetBar.TabStrip (Product Version 7.4.0.4). Moving between tabs is fine but I can't close the tab - the 'X' at the far right of the TabStrip (which does the close) is n...
  • Colin_McCrae's avatar
    Colin_McCrae
    9 years ago

    As long as location relative to parent/associated object is consistent, using an offset and co-ordinate click calculated at run time is fine. I have to use them with a customised checkbox tree list. It has some custom event handlers that only trigger with a click event in the right place (over the checkbox). Only  way to activate it is to use an offset derived from the co-ordinates of the tree node text of the node you want. But it's always calculated during the run, using retrieved co-ordinates of the text node container. Works perfectly.

     

    Hard coded co-ordinates however, are a recipie for disaster ....

subbu_valliappa's avatar
subbu_valliappa
Contributor

Yes, I thought about the offset method as the "X" would be always at the top right corner. That is probably the best option for now as I couldn't find any "Close", "Exit" or "Quit" method for the tabstrip object.

Colin_McCrae's avatar
Colin_McCrae
Community Hero
9 years ago

As long as location relative to parent/associated object is consistent, using an offset and co-ordinate click calculated at run time is fine. I have to use them with a customised checkbox tree list. It has some custom event handlers that only trigger with a click event in the right place (over the checkbox). Only  way to activate it is to use an offset derived from the co-ordinates of the tree node text of the node you want. But it's always calculated during the run, using retrieved co-ordinates of the text node container. Works perfectly.

 

Hard coded co-ordinates however, are a recipie for disaster ....