From 4a49ba509bdc0b4ffa650fc8461738c2085161c7 Mon Sep 17 00:00:00 2001 From: Mason Reed Date: Sun, 13 Jul 2025 14:39:14 -0400 Subject: [WARP] Add network container This is going to be disabled by default on this upcoming stable, however users may enable it once we deploy the public server. The data from the server is done through `Container::fetch_functions` independent of the nonblocking function lookup functions. The sidebar has been updated to drive fetching so that when users navigate to a new function the fetcher will kick off. This fetcher operates on a separate thread, in the event of a user navigating to many functions before the current fetch has completed they all will be batched together in a single fetch. Networked container currently is limited to just function prototypes, other type information separate from the function object will be omitted. --- plugins/warp/ui/plugin.cpp | 3 +++ 1 file changed, 3 insertions(+) (limited to 'plugins/warp/ui/plugin.cpp') diff --git a/plugins/warp/ui/plugin.cpp b/plugins/warp/ui/plugin.cpp index 69aaaf34..923a79b3 100644 --- a/plugins/warp/ui/plugin.cpp +++ b/plugins/warp/ui/plugin.cpp @@ -170,6 +170,9 @@ void WarpSidebarWidget::notifyViewChanged(ViewFrame *view) void WarpSidebarWidget::notifyViewLocationChanged(View *view, const ViewLocation &location) { + // Warp sidebar really should only update if it is visible, otherwise its a waste of cycles. + if (!this->isVisible()) + return; auto function = location.getFunction(); // TODO: Only update if the function exists? // NOTE: The function called will exit early if it is the same function. -- cgit v1.3.1