Viewing 3 posts - 1 through 3 (of 3 total)
Author
Posts
  • #4563

    I’m looking at results from a search and see the year of death written as 1,365 and 1,499. Not sure why there are commas. Then I realize it’s telling me how many years ago the people died. Just happens it’s the column that I see more than the actual birth year.

    Personally, I’d rather the space be given over to Place which is often very cramped. Same too for death.

    -----
    [updated: 11 Jun 2021]
    MacOS: 10.15.7  (Catalina)
    Safari   14.0.3;  Firefox 89.0
    PHP 7.4 FastCGI

    Alter-Drukarsh connections... 3.3.8 <private>
    The Royals 3.3.8<royals.rbcsolutions.ca
    >
    The Gerrer Rebbes 3.3.8 <royals.rbcsolutions.ca/index.php?ged=rebbes>

  • #4564

    There are no width parameters controlling the width of any of those columns. They each take as much space as they need, only using more if it’s spare after all the columns are rendered, starting from the left and working across. That does mean that the last (place of death) will often be wrapped.

    Its not practical to set column widths given the infinite variations on content (data) length, screen size, theme design, screen font and zoom settings, etc..

    Similarly forcing a “nowrap” policy on (for example) the place names could get crazy when some people have place levels extending to 6 or even nine parts. Even on my site with a maximum for any place of three levels it results on the table extending wider than the screen unless I go full screen on my 27 inch monitor!

    So the only solution is to physically remove the two “anniversary” columns. Even that will only improve things for some situations, not others, and simply leave a lot of white space for many. Those columns have been there since PGV was invented. It would need a major user consensus to remove them.

    Also, that display is common to other parts of the system, especially the individual list pages. So any change will effect those too – and I wouldn’t want to start creating more display variation than necessary.

    As is often the case, the most common problem with busy displays like that is small screen sizes and / or large fonts / zoom settings.

    Nigel
    My personal kiwitrees site is www.our-families.info
  • #4569

    <QUOTE>…small screen sizes and / or large fonts / zoom settings….

    Let’s face it, you and other developers are caught “between a rock and a hard place”!

    Mobile devices are small screens. Accessibility standards are large fonts and/or zoom capabilities. Yet the mobile generation is taking over. I hear desktops will soon be thing-of-the-past 🙁 Don’t misunderstand, kiwi, kt mobile will be very handy. What drives me cray is mobile browser is not scaled down from desktop, it has so much less functionality. Yet very handy.

    -----
    [updated: 11 Jun 2021]
    MacOS: 10.15.7  (Catalina)
    Safari   14.0.3;  Firefox 89.0
    PHP 7.4 FastCGI

    Alter-Drukarsh connections... 3.3.8 <private>
    The Royals 3.3.8<royals.rbcsolutions.ca
    >
    The Gerrer Rebbes 3.3.8 <royals.rbcsolutions.ca/index.php?ged=rebbes>

Viewing 3 posts - 1 through 3 (of 3 total)
  • The topic ‘Search results’ is closed to new replies.