Hi Mick,
Sorry about that. The code below does work, however, in my case its a
little more complex. I'll try and explain. I've put most of the code
into different modules which get imported in the usual way, so I have
one that has all the classes for the menu bar. There is also a class in
her
Hi Iain,
My earlier reply established that the radio widget IS functioning correctly
on your machine in the usual case. If there is still something wrong, I'd have
to see runnable code from your app which fails to set the radio. Can you
make a minimal case which uses the class structure you disc
Dear Alex,
I think you are on to a valid solution: tag each anchor.
I would use 2 tags:
1) A general tag called for example 'link', which you config
a) to present itself as a link (e.g., in blue, underlines)
b) to respond to events, e.g., ButtonRelease
2) a tag for each individual l
You know, I think this is exactly what I was looking for.
Thanks for your help!
Mick O'Donnell wrote:
>
> Dear Alex,
>
> I think you are on to a valid solution: tag each anchor.
>
> I would use 2 tags:
>
> 1) A general tag called for example 'link', which you config
> a) to present
