tooltip latency

[dunbarx]

The toolTipDelay determines how long it takes for the toolTip to appear.

But its appearance times out after about 5 seconds. Is this a property one can set, to keep it open?

Craig

[richmond62]

Do you man that, once a toolTip has appeared you want it to keep being shown for some time longer
than 5 seconds?

If so, this has nothing to do with the toolTipDelay.

We have been down this alley-way before:

https://forums.livecode.com/viewtopic.php?t=34165

[dunbarx]

Richmond.

This never had anything to do with the toolTipDelay. I was asking about a possible "toolTipLatency"

The other thread deals with the placement of the actual toolTip, and workarounds. This was left to the team to mull over.

I do not expect any movement on this, I just wanted to know if I was missing something. A tooltip is supposed to be ephemeral, and five seconds likely seemed like the right amount of time, er, at the time. I will just change from a toolTip to an actual field, opened in the same way, and dismissed by hand.

Craig

[richmond62]

Personally I would be happy if one could set the time a toolTip was displayed as not everyone
is quick enough to get a 5 second display.

[dunbarx]

Richmond.

So would I. The toolTip for this control happens to be rather lengthly, and cannot be read in only five seconds. This probably means a toolTip in and of itself is the wrong way to go.

Craig

[richmond62]

You could try what I suggested in the thread I referenced earlier.

[dunbarx]

Richmond.

No idea to what you refer. Where is there any discussion of how long a toolTip stays open? Or, for that matter, any discussion that says it might be a nice thing to be able to control?

Craig

[jacque]

The toolTip for this control happens to be rather lengthly, and cannot be read in only five seconds. This probably means a toolTip in and of itself is the wrong way to go.

I agree. One of my projects had a similar requirement that showed long explanations of images. We decided on showing a field on mouseEnter and hiding it on mouseLeave.

[dunbarx]

Jacque.

Right on. If done properly, the field can look and act just like a toolTip, but has the advantage of all the property options of fields.

It is one more control, of course, but that is a first-world problem.

Craig

[richmond62]

SShot 2022-07-29 at 18.42.32.png (7.18 KiB) Viewed 10736 times

-
Oddly enough the tooltip did NOT disappear UNTIL I moved the mouse again (even though
the pointer was still inwith the bounds of the object).

[FourthWorld]

Jacque.

Right on. If done properly, the field can look and act just like a toolTip, but has the advantage of all the property options of fields.

It is one more control, of course, but that is a first-world problem.

And arguably not much of a problem at all. You needed something that doesn't behave like an OS-spec tooltip, and built something that wasn't an OS-spec tooltip.

Sometimes we need things beyond common GUI conventions. Most of the time LC makes creating new types of GUI elements rather easy. Glad you found that to be the case with your project.

[spinabove]

I have absolutely no clue what you're talking about. I can't seem to find any information on how long a toolTip is shown. Or any talk that suggests it would be wonderful to have some voice in the matter?

[FourthWorld]

I have absolutely no clue what you're talking about. I can't seem to find any information on how long a toolTip is shown. Or any talk that suggests it would be wonderful to have some voice in the matter?

Much could be written about toolTips. Let's start with what's most relevant for you: what are you building with LiveCode?

And why Nord over PIA?

[richmond62]

This is a load of old cobblers:
-

-

Code: Select all

on mouseEnter
   set the lockScreen to true
   open stack "Tipper"
   set the topLeft of stack "Tipper" to the bottomRight of me
   put the short name of me into fld "ff" of stack "Tipper"
   set the lockScreen to false
end mouseEnter

OBVIOUSLY the thing is misunderstanding bottomRight [possibly relative to the screen rather than the stack].

[Klaus]

...
OBVIOUSLY the thing is misunderstanding bottomRight [possibly relative to the screen rather than the stack].

EXACTLY!
LC objects are located relative to the card, stack relative to the screen.