-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Stats/clock alignment issues #1
Comments
It's been developed on Chrome. I have no doubt that other browsers will make it look a little off. But with it just being used on one big screen, I figured it wouldn't matter much, we can just se chrome. If this is a screenshot of chrome, then I am not sure what is causing this... |
Yup, this is on Chrome, 15" Retina MBP running in non-retina mode (high res) |
Ok, thanks. Will have a word with Ruth and look into it. From: Cristiano Betta <[email protected]mailto:[email protected]> Yup, this is on Chrome, 15" Retina MBP running in non-retina mode (high res) — |
I'll check - but the design is not finished yet so things like alignment On Mon, Jul 15, 2013 at 10:12 AM, Sean Holden [email protected]:
|
@Rumyra yeah what I thought but thought I'd raise it |
Yeh see the fonts aren't working either - that column is too big... There's a million issues! The design is not finished. And anyway even if it was I still wouldn't say it was until I have done On Mon, Jul 15, 2013 at 10:45 AM, Rumyra (roo-my-rah); [email protected]:
|
@Rumyra I know it's not done! I'm just playing with it to see if I can use it for another event and I noticed this. No need to see my issues more important than your own list. I'm just listing a few things FYI. |
Its an issue that should be kept an eye on. We now have the board running on the big screen in the office so issues will start appearing :) It's pretty much un-readable at 12ft so some work to do. |
Yeh I can't do final tweaking until I see it on the big screen on Friday... I'm looking to get the overall design done by tomorrow - then tweaks Friday. On Mon, Jul 15, 2013 at 10:55 AM, Kevin Prince [email protected]:
|
Not sure if this was known but I thought I'd report it.
The text was updated successfully, but these errors were encountered: