I believe your's is the best possible fix right now.
IMO, the correct fix would be to have the set/isEnabled methods in the GUI just call the corresponding ones in the node.
But this would involve putting the JMeterGuiComponent.setNode method back in use, which looks like an Herculean job right now. I won't do it -- or not now. (Note this would fix another issue: the component name would be ported to the tree as you type it in the GUI, or so it seems from the NamePanel code).
I have a strong impression that all this code has too much history in its back and needs serious clean-up -- including reviewing the APIs and contracts. I'm thinking about the TestBean concept being able to replace all this mess...
-- Salut,
Jordi.
Jordi Salvat i Alabart wrote:
I touched this code section a few days ago, so it's probably my fault. I'll have a look...
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
