Family Historian User Group

Highlight complete selected row in 'Query Result Sets'

I agree, especially useful when there are too many Columns to fit a single screen, when moving too far to the right, causes column 1 to scroll left off screen.
Users define column headers, so why not allow them to define Row headers too, that when clicked could highlight whole row?
Another alternative would be to make Column 1 a Fixed column that doesn't scroll with rest of Columns

Croftian raised this in another topic recently and Mike pointed out that:

tatewise wrote: ↑

10 May 2023 19:12

That was discussed in [Wish List Reference 567] Highlight complete selected row in Records Window (17298) and resulted in Wish List Ref 567 Highlight selected Row(s) in Records Window which was closed when partially implemented in FH V7.0.
Unfortunately, although mentioned in both the discussion thread and the Wish List entry, the Query Result Set row highlighting was not implemented. However, that gives the format for raising a Wish List entry for Query Result Sets.

I wonder if CP simply didn’t notice the line in the previous wish list item which said “A similar Row highlighting feature should be added to all tabulated lists such as the Query Result Set window.” I assume it would be no harder to implement there than in the Records window.

I've changed the Subject to include Plugins as it was a Plugin Result Set that prompted the OP to raise the issue.
See Places & Addresses Wed 10th May 2023 18:49

Mike, there is already Wish List Ref 290 Lock the Column(s) in Records Window which like Wish List 567 only says the Records Window in the Title but mentions the Query Result Set in the details. We don't want the same partial implementation to happen again!

So how do we proceed?
Do we create two new Wish List entries for Query and Plugin Result Set and all similar lists requesting (1) row highlighting and (2) column locking, or do we amend the existing two Wish List entries?
New entries risk diluting the Votes between Records Window and Query/Plugin windows, whereas amending them risks misrepresenting the existing Votes.

The problem is that no.567 has been marked “Released in Version 7.0” so has, in effect, been closed.

I’d suggest

• Create a new item for highlighting rows in the Query and Plugin Result set (mentioning that this has already been implemented for the Records window)
• Amend Wish List item 290 (locking first column) to include Query and Plugin result sets as well as the Records window.

Each could refer to the other, as they are related.

I wasn’t aware of previous wish list on similar topic. I’m happy to leave it to whichever way you’ll feel will get best outcome

Has anyone asked CP if they think they've already done it (i.e. is it a bug?)

How would we know? CP don't publish their Support Tickets and planned fixes.

tatewise wrote: ↑

16 May 2023 10:35

How would we know? CP don't publish their Support Tickets and planned fixes.

The key word I used was 'asked'. Has anyone raised a ticket?

Sorry, I thought the keyword was 'anyone'.
How would we know if anyone has asked CP or raised a ticket on that topic?
That could be anyone in the whole wide world. I'll send out a polling request to them to see if they have asked CP.

Oh! Perhaps you meant just the three people who have contributed to this thread.
Well clearly not, otherwise we would not be posting here for a Wish List entry!

tatewise wrote: ↑

16 May 2023 10:54

Oh! Perhaps you meant just the three people who have contributed to this thread.
Well clearly not, otherwise we would not be posting here for a Wish List entry!

Four of you actually, if we're being pedantic.

And because I'm clearly not being clear enough for you, Mike:

Why doesn't one of you raise a ticket with CP to ask if the absence of this is by design, or a problem with the implementation?

I have now managed to find the reference to this in CP's release notes (v7.0.9)

Previously you had to click on the text in the first column of many lists (e.g. record lists), to select that item. Now by default, you can click on any text in any column and the whole row displays as selected. Some lists, such as record lists, have a little ‘+’ in a box which allows details to be expanded. “Full row selection” only applies to unexpanded rows. Users who preferred the old way, can revert to it by unticking a new option ‘Prefer Full Row Selection’ (ticked by default) in the ‘Advanced’ area of the General tab of Preferences.

It doesn't explicitly mention Query or Plugin Result sets, but is worded in a way which suggests they ought to be covered.
I'll ask CP about it.

I have raised ticket #382202 Highlight Result Set Rows.

I have edited Wish List Ref 290 Lock the Column(s) in the Records Window, Result Sets, etc to explicitly include Query and Plugin Result Sets.

The CP response to my ticket #382202 Highlight Result Set Rows is:
"It is a wish list request that has not been implemented. If you are asking if we are we planning to do it, I'm afraid we do not give out that sort of information. Sorry not to be more helpful."

So what do we do?
CP say that Wish List Ref 567 Highlight selected Row(s) in Records Window has not been implemented but it was closed when partially implemented in FH V7.0.
Do we re-open it or raise a new Wish List entry?

They sent me the same response. I had quoted the paragraph from the 7.0.9 release notes and asked if it was an oversight that it was not implemented for Query and Plugin Result sets (as the paragraph seems to suggest it would be) but they didn't comment on that.

I suppose we should just re-open Wish List Ref 567, because that way it will keep the existing votes.

Mike should reopen the wish list, amended to reflect what has already been done and what is outstanding (possibly woith an amended title).

I think I have done that with a revised Title and moved to General category. Let me know if anything is not OK.

LornaCraig wrote: ↑

16 May 2023 15:28

I had quoted the paragraph from the 7.0.9 release notes and asked if it was an oversight that it was not implemented for Query and Plugin Result sets (as the paragraph seems to suggest it would be) but they didn't comment on that.

That’s not untypical of CP support, unfortunately. If it’s something they are happy to discuss, they can be very helpful, but if not, they tend to just ignore the question. Not great, but I suppose “sorry, we don’t want to talk about that” could get a bit repetitive.

Closed as now explicitly covered in Wish List.