Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Structure GUI improvements

Open
#228 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp, python
Domain
frontend

Research direction

Start with the Structure GUI build method and the relevant structure class headers described in the issue; no specific files or tests are named. Define the scope of an official structure-customization mechanism and built-in UI customization, then confirm the resulting API avoids the current type-casting workaround.

Written by the indexing model from the issue text.

Description

I'm working mainly off the Python version but have been wanting UI customizations and so have been making changes to the C++ side and rebuilding the wheel. One of the things I've had to implement so far is customization for how the Structure GUI adds structures to itself. Right now it adds structures by the typeName, which itself is a hardcoded string in the respective structure class and set as a static variable. It's used all over the place in that context so I ended up adding a defining a new var setting it all in the header for the structure class I wanted to customize the GUI for, then modifying the structureGUI build method to check for this new var and set it in a collapsing header by that instead of its typeName. In the end my solution is kind of hacky and relies on type casting. I would like to request a more official implementation of this feature as well as more customizability for UI elements, etc. as built in.

Dominant language
C++
Stars
2.2k
Forks
242
Avg merge
11m
Merged PRs (30d)
1

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nmwsharp/polyscope

All issues in nmwsharp/polyscope

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.