Skip to content
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

Vertical lines or some other division devise #13

Open
goodhandd opened this issue Mar 4, 2013 · 2 comments
Open

Vertical lines or some other division devise #13

goodhandd opened this issue Mar 4, 2013 · 2 comments
Assignees

Comments

@goodhandd
Copy link
Contributor

Was speaking to an educated user (knows all about noise predictions etc.).

What he initially started to do was enter the distance to receptor in the reference box. He didn't look properly though. But, it may be an idea to define "Noise source" "site environment" and "SPL at receptor" sections for each plant a bit better. This may be helpful for plant way down the list that are quite detached from the headers.

Maybe not. What do you think?

@ghost ghost assigned stephband Mar 4, 2013
@stephband
Copy link
Member

Those headers should probably be sticky headers. That is, they should stick
to the top of the window when the hit it and remain there while the rest of
the content scrolls underneath.

On 4 March 2013 14:13, Daniel Goodhand notifications@github.com wrote:

Was speaking to an educated user (knows all about noise predictions etc.).

What he initially started to do was enter the distance to receptor in the
reference box. He didn't look properly though. But, it may be an idea to
define "Noise source" "site environment" and "SPL at receptor" sections for
each plant a bit better. This may be helpful for plant way down the list
that are quite detached from the headers.

Maybe not. What do you think?


Reply to this email directly or view it on GitHubhttps://github.com//issues/13
.

@goodhandd
Copy link
Contributor Author

Yes

On 6 Mar 2013, at 03:47, stephband notifications@github.com wrote:

Those headers should probably be sticky headers. That is, they should stick
to the top of the window when the hit it and remain there while the rest of
the content scrolls underneath.

On 4 March 2013 14:13, Daniel Goodhand notifications@github.com wrote:

Was speaking to an educated user (knows all about noise predictions etc.).

What he initially started to do was enter the distance to receptor in the
reference box. He didn't look properly though. But, it may be an idea to
define "Noise source" "site environment" and "SPL at receptor" sections for
each plant a bit better. This may be helpful for plant way down the list
that are quite detached from the headers.

Maybe not. What do you think?


Reply to this email directly or view it on GitHubhttps://github.com//issues/13
.


Reply to this email directly or view it on GitHub.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants