search

UCL / HHyeast-server

0 stars 0 forks source link

Panning visualisation using mouse to drag - goes beyond ends of protein #49

Open timlevine opened 6 years ago

timlevine commented 6 years ago

when I drag the screen either direction, the bar indicates the proteins goes on for ever in both directions. Can it be set to only go from 1 to the end? Thanks, T

ilectra commented 5 years ago

It seems it makes sense to remove the panning tool from the summary view, and restrict it to only the y direction for the detail view. @timlevine , do you want similar constraints for the wheel zoom tool, or should I remove it completely?

timlevine commented 5 years ago

Some of these pages are a joy - for example http://hhyeast.ukwest.cloudapp.azure.com:5000/YFT2/yeast

which very beautifuuly shows the basis of a paper from my lab in 2017 where we scooped our opposition!

I have never ever got the hang of the wheel! How can I use it on a MacBook?

I’ve just looked at http://hhyeast.ukwest.cloudapp.azure.com:5000/YPR097W

Overall this is much clearer and more intuitive. I found some issues - general and specific: general:

  1. you mentioned once having a download file button on the pages - not having to go to the very start and enter a name + press download file. users will struggle to go round that loop. Did you tell me that this would be dropped!?

  2. Changing the parameters produces a lot of text - can the word cluster” be replaced with “#” and drop all “ :” to compress it a bit.

specific:

  1. hit in Pfam PF00787 should be to columns 470-499 - in line with the hits in the other windows (1O7K, ad Ypt35). Good luck trying to find the bug for that!

On 27 Sep 2018, 17:18 +0100, Ilektra Christidi notifications@github.com, wrote:

It seems it makes sense to remove the panning tool from the summary view, and restrict it to only the y direction for the detail view. @timlevine , do you want similar constraints for the wheel zoom tool, or should I remove it completely? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.