Update geometry from UI parameter

Open
#215 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
cpp

Research direction

Start at the shown UICallback, especially ImGui::InputInt("Sides") and polyscope::state::userCallback, and trace how sides is expected to reach mesh generation and the viewport. Done means changing Sides in the UI visibly regenerates or updates the mesh; the issue does not name a file or test to run.

Written by the indexing model from the issue text.

Description

I have this UI callback to control how a mesh is generated but changing it in the UI doesn't affect the mesh in the viewport.
What am I missing? I can't find any documentation about this. Thanks.

int sides = 6;
void UICallback()
{
  bool changed = ImGui::InputInt("Sides", &sides);

}

// In main:
  polyscope::init();
  polyscope::state::userCallback = UICallback;
  polyscope::show();
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.