A limitation of our current recorder implementation is that it only supports SWT widgets. we have a bit of work to do to make it recognize custom widgets such as the one you are trying to record.
In the short term, you should be able to work around this limitation in the runtime by hand-writing your locators. Ideally you could also name the widgets so that they are easy to identify. For instance, if you named your PlannerText widget "c2bm.ddp.client.widgets.PlannerText" you could click it in a testcase as follows:
- Code: Select all
For more on naming, see this FAQ entry:
http://downloads.instantiations.com/Win ... e_a_widget
(Incidentally, if the widget is so named, you should also sidestep the classnodef exception you're seeing since the recorder will use the name and will not need to refer to the class -- bonus!)
Let us know if this works for you. Either way, if recording events on unnamed custom widgets is a high ticket item for you, please submit a feature request to: