Hi folks,
Trying to replicate HTML a links within a LiveCode field. The docs describe
'set the textStyle to link' to create the link a/ tag itself and 'set the
linktext to uri' provides the 'href' parameter.
But is there an equivalent of the HTML link title parameter at the field/text
level?
On Jul 5, 2011, at 4:41 AM, Keith Clarke wrote:
Hi folks,
Trying to replicate HTML a links within a LiveCode field. The docs
describe 'set the textStyle to link' to create the link a/ tag
itself and 'set the linktext to uri' provides the 'href' parameter.
But is there an equivalent of the
Thanks for the steer Jim. Just to be clear, I'm not looking for HTML
compatibility - I was using the a link description as an analogy to describe
the required behaviour. It's the effect of a tooltip on text within a field
that I want to create (and it's good to know that this is not a standard
On 7/5/11 6:41 AM, Keith Clarke wrote:
Hi folks, Trying to replicate HTMLa links within a LiveCode field.
The docs describe 'set the textStyle to link' to create the linka/
tag itself and 'set the linktext touri' provides the 'href'
parameter.
But is there an equivalent of the HTML link title
Keith Clarke wrote:
I was using the a link description as an analogy to describe
the required behaviour. It's the effect of a tooltip on text
within a field that I want to create (and it's good to know
that this is not a standard thing that I have simply overlooked).
I've tried the message
On 7/5/11 11:22 AM, J. Landman Gay wrote:
On 7/5/11 11:15 AM, Richard Gaskin wrote:
Keith Clarke wrote:
I was using the a link description as an analogy to describe
the required behaviour. It's the effect of a tooltip on text
within a field that I want to create (and it's good to know
that
Or to embed the tooltip with the link:
a href=tooltip:Some text to displaySome text/a
on mousemove x,y
set itemdel to :
get the linktext of the mousechunk
if item 1 of it = tooltip then
set the tooltip of me to item 2 to -1 of it
else
set the tooltip of me to
Thanks Jaque, Jim and Richard for the insights - you've given me the necessary
ingredients for a workaround.
I'm surprised that such measures are necessary for a net-aware development
environment - and I can't find any requests on the QA forum to address this
issue.
So, I've added this
