Fuzziness is a good description, but things stand in sharper relief today. I
was more focused on the syntax than the mechanics and for no particular reason
started out with collections. Converting the app to an entity selection
approach is turning out to be much easier than expected,
a) It seems that there is some fuzziness in the way Entity Selections and
Collections are understood. Let's try to make it more precise:
- An Entity selection doesn't 'contain' the Entities, it's a List of Entity
References (in this case, a reference is a 4D internal référence
On Tue, Apr 16, 2019 at 11:53 AM Keith Culotta via 4D_Tech <
> It's looking like it can all be done with entity selections, and be more
San Francisco, CA
What can be said, can be said clearly,
Interesting stuff, especially how entitySelection.toCollection duplicates data.
I'm currently displaying collections in the listbox. It's looking like it can
all be done with entity selections, and be more efficient.
Keith - CDI
> On Apr 16, 2019, at 12:53 PM, Kirk Brooks via
You know you can go about this from another point of view. I actually
posted about this a bit ago. This won't accomplish exactly what you are
asking for but it may be something you can use.
First, remember that even when you have a very large collection or entity
selection, as you seem to,
That seems promising. Since the listbox is a collection/entity selection, each
row's color would be set by the rows presence in the "Selected items"
collection. I imagine the performance would be OK as long as the search only
took place as the row becomes visible to the User.
I just started a Feature Request for this:
Take a look and see what you think. Collection/entity based listboxes are a
very different animal from array or selection based ones. And the way to
work with them is different too. Frankly the easiest thing
Checking the listbox's Property "Hide extra blank rows" stopped 4D from
unexpectedly quitting when using
LISTBOX SELECT ROW(*;"valsBox";0;lk replace selection) // and it's fast
just having a lot of rows to highlight in a loop.
The crashing showed up more often in compiled mode before
How about this - rather than change the highlight, what about just changing
the color of the rows to mimic that they’re selected? You can still
maintain array of record numbers/ID’s that represent the selection but just
update the UI so that it looks like the rows are selected.
Thank you for the suggestion.
I switched the deselect-all code to
LISTBOX SELECT ROW(*;"valsBox";1;lk replace selection)
LISTBOX SELECT ROW(*;"valsBox";1;lk remove from selection)
and the selection did clear, however as soon as this add-to-selection code is
On 16 Apr 2019, at 5:04 am, Keith Culotta via 4D_Tech <firstname.lastname@example.org>
> I'm looking for a fast way to highlight a selection of rows in an entity
> selection listbox. The way I am aware of works OK unless the listbox gets a
> large number of rows.
I'm looking for a fast way to highlight a selection of rows in an entity
selection listbox. The way I am aware of works OK unless the listbox gets a
large number of rows.
Adding records to the Selected Items name in the Property list does not
highlight the listbox contents. The
Mail list logo