Page 1 of 1

Mabe a bug: In Search results: No live status of cloud-based items

Posted: 05 Jul 2024 11:35
by autocart
Hi Don,
just a small issue: Status of cloud-based items in search results:

Properties, like "modified date" seem to be live in the search results (they update automatically if the value for the file changes). (At least, I just tested the "modified date".)

However, as I just found out, the status of cloud-based items does not update in search results (on my system), as the "modified date" does.
Not sure if should or if the status of cloud-based items is supposed to be just a snapshot in a search results list.

regards

Re: Mabe a bug: In Search results: No live status of cloud-based items

Posted: 06 Jul 2024 10:35
by admin
autocart wrote: 05 Jul 2024 11:35 Properties, like "modified date" seem to be live in the search results (they update automatically if the value for the file changes). (At least, I just tested the "modified date".)
Sure? AFAIK auto-refresh is suspended in search results.

Re: Mabe a bug: In Search results: No live status of cloud-based items

Posted: 08 Jul 2024 10:07
by autocart
Maybe that is the same issue then, as in my "problem" with the branch view.

Whenever I switch tabs back and forth (coming back to the search results), it automatically triggers a refresh of the search, even though, the "Suspend Auto-Refresh" in the "View" menu is (automatically) ticked. IMHO, coming back to the search results tab (or branch view tab) should not trigger anything, unless there was a switch by which I did specifically tell it to do so.

Re: Mabe a bug: In Search results: No live status of cloud-based items

Posted: 08 Jul 2024 10:14
by autocart
ok, update:

just realized, that in a fresh instance, it behaves differently (I am always talking about a tab change):
  • modified dates are still updated.
  • missing files are deleted from the list.
  • new (or renamed) files are not listed.
But why does it still trigger a repeat of the search in my production instance? I do not know any ideas?
UPDATE: Ok, it seems to be because I turned off "cache search results". Well, this feature still has "air to above" (room for improvement) from a users point of view. :kidding: