default `name=` in `register_surface_mesh` ?

Open
#25 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
42/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
python

Research direction

Start at the register_surface_mesh entry point named in the issue and inspect how repeated registrations use the name argument. Done means the default-name question has a consistent implemented answer, including defined behavior when the function is called repeatedly without a meaningful name.

Written by the indexing model from the issue text.

Description

When using polyscope for a quick visualization I don't always have or care about a meaningful "name" for my mesh. Could there be a default?

If I understand correctly calling register_surface_mesh twice with the same name will overwrite the first call's data. So I guess there's a question whether a default would be default1, default2, etc. or just keep overwriting default. I kind of like overwriting default because avoiding that clearly gives the non-default name a sense of purpose.

Dominant language
C++
Stars
53
Forks
25
PR merge metrics
No merged PRs in 30d

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-py

All issues in nmwsharp/polyscope-py

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.