Ha! - d’you know Jeff, I had considered exactly this maybe a half-dozen times! Each time however, a little voice inside my brain said “Nah, don’t be dumb, of course they’re exactly the same thing!”
Interesting how Set Text still works though.
But I had a bit of an epiphany two days ago:
- Most people are familiar with using hidden, carefully-named widgets to act as local variables
- Why not use hidden, carefully-named buttons to act as custom-named functions?
- All you need do then, is to fire Click from other widgets when you want to activate the named function
Well as it turns out this works spectacularly well. It essentially forces you to create a “Debug UI” for your prototype. All the “variables” can be on display as you run it, and you have buttons to manually test every custom function you’ve written - works like a charm. You can even group the controls and make them visible/invisible based on the status of a global variable called “debug” or somesuch.
There is a point at which the point-and-click code-builder and associated function editors within Axure start to seriously slow down prototype development.
Thanks everyone as always for your help on this (and other) matters.