Custom component help

SmartBear Support wrote:

euthenia wrote: Hi! Nice to see a fellow component developer! First of all, for your attached script to work, you need to include a header in it, similar to the one below: /** * @name Stepped Rate * @category generators * @nonBlocking true */ What's important above is @category runner. You probably know this already since you got the component to show up in loadUI. I have tried to reproduce the problem, but I'm unable to. I'm trying this: 1. Set your component to Starting rate 1, Increase 1 and Interval 10. 2. Play project (everything works). 3. While playing, change starting rate to 3. 4. Actual rate is set to 3 automatically and increases from there. Starting rate stays at 3, as far as I can tell. I'd be glad to help if I could reproduce this. Regards Henrik SmartBear Software

Thanks for the reply. I do actually have a header in my component - I just omitted it when I pasted the code in to my original post. Interesting that you don't seem to have the same problem as me... What I've tried is:

1. Set starting rate to 1, unit to 'Sec', increase to 7, interval to 3 and interval units to 'Sec'.
2. Hit play and let it tick up a bit.
3. Change the starting rate (either change it to some other value and leave it there or just move it and move it back).
4. The actual rate is reset to the starting rate.
5. The starting rate now starts increasing by itself.

I've added some logging in the component to see what is happening. If you have the log showing, you should see logging of the form 'Current rate: x, stepIncrease: y' each time the interval elapses, and should only see logging of the form 'Starting rate changed to: x' when the starting rate is manually changed. I'm getting lots of logging about the starting rate changing when I haven't made any change to it myself. As I said, this only happens if I change the starting rate while the test is running.

It's not the end of the world for me as for my purposes I don't think that I would be changing the settings while a test is running, but it limits the usefulness of the component somewhat and means that I'd be hesitant to submit it to you for featuring in the custom component gallery because it's badly behaved.

I'm using loadUI 1.5.0 by the way as we ideally need to be using released software rather than a nightly build.