Earlier quoted context omitted.
On a Catholic church site I designed you have to do the cross pattern with your mouse and say 3 Hail Marys to see the tooltip. There is no contact form. Only a Confession Textarea
At least the cookie popup comes with wine
Tooltips need a delay, and then they need to skip it
51–60 of 92 posts
Re: Tooltips need a delay, and then they need to skip it
#52I think I would describe this as an example of hysteresis. Neat! https://en.wikipedia.org/wiki/Hysteresis
Re: Tooltips need a delay, and then they need to skip it
#53Re: Tooltips need a delay, and then they need to skip it
#54I think I would describe this as an example of hysteresis. Neat! https://en.wikipedia.org/wiki/Hysteresis
>> Hysteresis is the dependence of the state of a system on its history. For example, a magnet may have more than one possible magnetic moment in a given magnetic field, depending on how the field changed in the past. How is this different from the observation that, say, a non-magnetic iron ball may have more than one possible velocity in a given gravitional field, depending on whether it was recently thrown upward o…
A chunk of iron put into a 1μT magnetic field will behave differently depending on what other magnetic fields it has been in recently.
Re: Tooltips need a delay, and then they need to skip it
#55I think I would describe this as an example of hysteresis. Neat! https://en.wikipedia.org/wiki/Hysteresis
Re: Tooltips need a delay, and then they need to skip it
#56I think I would describe this as an example of hysteresis. Neat! https://en.wikipedia.org/wiki/Hysteresis
>> Hysteresis is the dependence of the state of a system on its history. For example, a magnet may have more than one possible magnetic moment in a given magnetic field, depending on how the field changed in the past. How is this different from the observation that, say, a non-magnetic iron ball may have more than one possible velocity in a given gravitional field, depending on whether it was recently thrown upward o…
Re: Tooltips need a delay, and then they need to skip it
#57Re: Tooltips need a delay, and then they need to skip it
#58It will never cease to amaze to me that Apple (under Jef Raskin who also wrote about this in The Humane Interface) observed and fixed problems with interactions like this in SYSTEM 6 in like 1993 or something - only for the same problem to have to be re-descovered and re-fixed decades later.
Raskin left Apple in 1982.
(Raskin left before even the original macintosh he helped lead. He also opposed the use of the mouse)
Re: Tooltips need a delay, and then they need to skip it
#59It will never cease to amaze to me that Apple (under Jef Raskin who also wrote about this in The Humane Interface) observed and fixed problems with interactions like this in SYSTEM 6 in like 1993 or something - only for the same problem to have to be re-descovered and re-fixed decades later.
I like how these things are "figured out" and then fleshed out bit by bit like they're some kind of innovation. Software industry in a nutshell.
Re: Tooltips need a delay, and then they need to skip it
#60I'm always amazed by solutions for user interactions. I once built a Bomberman clone that had control issues. The first iteration of the controls were clunky, because I only checked if a player was touching a block in the direction they wanted to move and if there was, I reset the position. Move down, hit block, stop. After a bit of experimenting I checked if a player was halfway behind or ahead of a block and added…
A lot of new creators of course will not believe you if you tell you have to do these affordances. I once tested a person's multiplayer map where a door had a central lip that crushed you if you entered off-center. I told them that it should be fixed, but the answer was "you should always go through doors through the center". It's some sort of very enticing idea of purity. "My map will only have real architecture and no affordances." In the end it will self correct.