Skip to content

fix: use distinct icon for collections info panel#870

Merged
EdwardMoyse merged 1 commit into
HSF:mainfrom
rx18-eng:fix/distinct-panel-icons
Apr 9, 2026
Merged

fix: use distinct icon for collections info panel#870
EdwardMoyse merged 1 commit into
HSF:mainfrom
rx18-eng:fix/distinct-panel-icons

Conversation

@rx18-eng
Copy link
Copy Markdown
Collaborator

@rx18-eng rx18-eng commented Apr 1, 2026

Collections info and geometry browser both used the same info icon, making them hard to tell apart in the toolbar. Changed collections info to use the eventData icon (which already existed in assets but was unused). Also fixed the SVG id in both asset copies (Capa_1 -> eventData) so the fragment reference actually resolves.

Screenshot 2026-04-01 160005

@rx18-eng rx18-eng requested review from EdwardMoyse and sponce April 1, 2026 10:35
@sponce
Copy link
Copy Markdown
Collaborator

sponce commented Apr 3, 2026

Thanks for this. Just a stupid question : I do not get what I see in the file changed. It seems that the EventData icon has some change, although it looks exactly the same. Do you get it ?

Signed-off-by: rx18-eng <remopanda78@gmail.com>
@rx18-eng rx18-eng force-pushed the fix/distinct-panel-icons branch from 6d015ce to 7cbb895 Compare April 6, 2026 06:41
@rx18-eng
Copy link
Copy Markdown
Collaborator Author

rx18-eng commented Apr 6, 2026

Yeah the icon graphic itself is the same - the only change in those SVG files is the id attribute (Capa_1 -> eventData). The menu-toggle component references icons using a fragment URL like eventData.svg#eventData, so the SVG root element's id needs to match the icon name. The old id="Capa_1" meant the fragment reference didn't resolve and the icon was invisible. Also rebased the branch on latest main so the diff should be cleaner now.

@EdwardMoyse
Copy link
Copy Markdown
Member

Good idea. Thanks!

@EdwardMoyse EdwardMoyse merged commit c6cd0ff into HSF:main Apr 9, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants