English > Feature Suggestions

Minor Suggestions

<< < (2/3) > >>

buah:
I see and I agree. This issue obviously depends on how we decide to read whole content. I always read viewable content, than decide if it is "worthy" to expand it. From this point of view came my suggestion.

mgpw4me@yahoo.com:
So maybe the page should scroll automatically when the expander is clicked.  For long lists, like filmography or cast lists, the first line on the page would be the first line in the list, or the first previously non-viewable line.  I don't really have a preference, but have noted that expanding fields usually involves me scrolling to view the data.  One solution might be to scroll to the first line of the text, then have a marker on the first 'non-viewable' line...color change, graphic, space, line, whatever.

rick.ca:

--- Quote ---One solution might be to scroll to the first line of the text, then have a marker on the first 'non-viewable' line...color change, graphic, space, line, whatever.
--- End quote ---

This idea I like. Do you have any idea how the marking might be implemented? Also, after a page-down, it would be nice if the the previous last visible line becomes the first visible line. This would help a lot with the continuity of reading a memo field where the break occurs mid-sentence.

Another possibility, instead of scrolling a full page, is to scroll only so the first line of the previously not-fully-visible field is at the top. The idea would be to scroll as soon as you get to a field not fully visible—and it would jump to the top of the screen. If such a field uses more than a screen, then the current behaviour would apply. I'm guessing it might be easier to detect and handle a whole field, rather than detect and mark a line within a field.


--- Quote ---So maybe the page should scroll automatically when the expander is clicked.
--- End quote ---

I don't think so. For such a basic function, it should not be assumed, "if the user wants this, he must also want that." If I want to scroll, I'll scroll. If I expand a field, I may only be interested in that field and what follows, but I'm equally likely to want what appears above it to remain on screen. Again, these are meant for the one-at-a-time control of fields. If the continuity of reading the entire record is the issue, the sensible thing to do is expand all fields.

patch:
A minor suggestion even if it is not really related to OP post

Further to locked thread
Is installing MSVCR71.dll into the pvd directory during installation as suggested by Microsoft still on the to-do list?

Perhaps adding it to the download page would be a start

nostra:

--- Quote from: patch on June 09, 2010, 12:41:29 pm ---A minor suggestion even if it is not really related to OP post

Further to locked thread
Is installing MSVCR71.dll into the pvd directory during installation as suggested by Microsoft still on the to-do list?

Perhaps adding it to the download page would be a start

--- End quote ---

OK, I'll change the installer for the next version.

Navigation

[0] Message Index

[#] Next page

[*] Previous page