Hi @AndyPayne and all,
When developing a Hops server with multiple components, organizing them into logical groups in the Grasshopper interface can be challenging.
Even when using the same category name, components often appear under separate tabs:
#Group hops function
CATEGORY = "Plots"
@hops.component("/group/function_0",
name="___",
nickname="___",
description="___",
category=CATEGORY,
@hops.component("/group/function_1",
name="___",
nickname="___",
description="___",
category=CATEGORY,
Despite using the same CATEGORY
constant, these components appear as separate “Plots” tabs in HOPS “Available functions”.
None of these methods successfully grouped the components under common tabs:
- Using consistent category strings
- Using
subcategory
parameter - Using forward slashes in category names (e.g., “Plots/function_1”)
Has anyone found a reliable way to group Hops components under a single tab in Grasshopper? Or is this a current limitation of the Hops/Grasshopper interface?
Related post : Organise hops-server components using flask Blueprints