playbar visibility

[TimeScience]

Any reason to not make controls disappear competently like other players (youtube/vimeo) do? (I asked Sarah and Mohammad and they agree too)

[gdunstone]

From a UI design perspective yes.
The controls will still be there, just not visible. its one of the requirements for me doing the hiding (I need to check whether the cursor is over the controls.
I could make it totally invisible, however it would be deceptive because the controls are still "there", just invisible and people could still click on them.

Making them only clickable once they are fully faded in isnt a good idea either, as the interaction would be clunky (trust me, waiting on transitions is clunky).

The difference between us and youtube/vimeo etc is that we interact with our player space (dragging image around, using the UI etc), whereas they do not need to, as the content is more "passive" (no need to interact with the player space).

I can make the controls more transparent than they are now if you want?

[TimeScience]

if they appear as soon as moused over then they couldn't be clicked on without the user knowing it could they?

…

-- ​ Tim Brown Research Fellow, Center for Plant Energy Biology Australian National University, Research School of Biology, Canberra ACT 0200 *bit.ly/Tim_ANU <http://bit.ly/Tim_ANU>* | tim.brown@anu.edu.au ​ +61 0419-006-102 ​ (m) | ​ Skype: *TimeScience*

On Fri, Feb 10, 2017 at 1:13 PM, Gareth Dunstone ***@***.***> wrote: From a UI design perspective yes. The controls will still be there, just not visible. its one of the requirements for me doing the hiding (I need to check whether the cursor is over the controls. I could make it totally invisible, however it would be deceptive because the controls are still "there", just invisible and people could still click on them. Making them only clickable once they are fully faded in isnt a good idea either, as the interaction would be clunky (trust me, waiting on transitions is clunky). The difference between us and youtube/vimeo etc is that we interact with our player space (dragging image around, using the UI etc), whereas they do not need to, as the content is more "passive" (no need to interact with the player space). I can make the controls more transparent than they are now if you want? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#9 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AC7OxJX8hDc8CdA3IgcDbmK9NHoZD5obks5ra8ffgaJpZM4L80AK> .

[gdunstone]

So you dont want the transition? I think this is getting into bad idea territory.

[gdunstone]

I think the current method is the least clunky way of doing things without sacrificing usability and visibility.

The user knows the controls are there, and they can see through them, they dont disappear too fast and they dont have unexpected interactions.

[TimeScience]

It just needs to disappear completely when not in use,

…

On 10 Feb 2017 3:42 PM, "Gareth Dunstone" ***@***.***> wrote: I think the current method is the least clunky way of doing things without sacrificing usability and visibility. The user knows the controls are there, and they can see through them, they dont disappear too fast and they dont have unexpected interactions. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#9 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AC7OxCL66AND2DcX75SAAYVvSyLSmvYgks5ra-rGgaJpZM4L80AK> .

[gdunstone]

Why, when you can still see through it? Also it gives the impression that the interface isn't there when it actually is

…

On 14 Feb 2017 10:28, "Tim Brown" ***@***.***> wrote: It just needs to disappear completely when not in use, On 10 Feb 2017 3:42 PM, "Gareth Dunstone" ***@***.***> wrote: > I think the current method is the least clunky way of doing things without > sacrificing usability and visibility. > > The user knows the controls are there, and they can see through them, they > dont disappear too fast and they dont have unexpected interactions. > > — > You are receiving this because you authored the thread. > Reply to this email directly, view it on GitHub > <#9 (comment)- 278856348>, > or mute the thread > <https://github.com/notifications/unsubscribe-auth/ AC7OxCL66AND2DcX75SAAYVvSyLSmvYgks5ra-rGgaJpZM4L80AK> > . > — You are receiving this because you were assigned. Reply to this email directly, view it on GitHub <#9 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AEDEeG9elQqi_JblSkltoqgCoe57qsCcks5rcOcUgaJpZM4L80AK> .