It is essential when creating and developing a ‘Theme’ or consistent looking work environment that the user is able to easily test different themes and designs across an entire Grid or Workspace.
A Theme Editor could help users edit elements that share identical attributes at a Grid or Workspace level.
The process could involve the following:
Copy an element e.g. a button
Open the ‘Theme Editor’
A button ‘field’ or new button is presented
Paste Style the attributes to be edited onto the new button
Edit the attributes
Select the level at which the changes will be applied e.g. ‘Grid’ or ‘Workspace’
Tap ‘Done’
Result:
MGP applies the changes made to every button with attributes that are identical to the attributes pasted inside the ‘Theme Editor’.
Thanks for the suggestion! I think the underlying problem you’re trying to solve is maintaining a consistent visual design across multiple Grids and Workspaces, and I agree that’s an important workflow.
That said, implementing this as a standalone “Theme Editor” would be difficult with the current architecture. To support it properly, MetaGrid Pro would need a full user component/style system, where objects can reference shared styles instead of each storing their own appearance independently.
With such a system, you could:
Create and save your own reusable styles.
Apply a shared style to any number of objects.
Edit the shared style once and have every linked object update automatically.
Optionally detach an object if you want to customize it locally.
This is similar to how shared styles/components work in professional design tools like Figma, and it would solve the use case you described in a much more robust and scalable way than matching objects based on identical attributes.
And good news is - we have already designed this system and it is waiting for implementation - will be available in 1.9 this autumn.