How to register a structure in nested show()
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Domain
- api, computer-graphics
Research direction
Start by tracing the ps::show(), ps.set_invoke_user_callback_for_nested_show(), and ps.register_surface_mesh() entry points using the provided callback example. Confirm the required registration sequence for a nested show, then verify that pressing “Show” displays the surface mesh in the second show.
Written by the indexing model from the issue text.
Description
Hey there,
as I can read, there is the possibility to do a nested show. That means one can call the ps::show() function a second time. Now I don't seem to understand what I need to do in order to register strutures in the second show. As an example I currently have the following code
`
def callback():
if psim.Button("Show"):
ps.show()
ms = pymeshlab.MeshSet()
ms.load_new_mesh(os.getcwd()+"/Experiment-78/Experiment-78+curvature.ply")
vertices = ms.current_mesh().vertex_matrix()
faces = ms.current_mesh().face_matrix()
ps.set_invoke_user_callback_for_nested_show(True)
ps.register_surface_mesh("first mesh", vertices, faces)
(This example is in python but the structure is sufficiently similar). Currently when I press the button the surface mesh is registered in the first show. What do I need to do in order to get it in the second show?
(I am happy about a solution in either C++ or python)
I hope you get what I mean
- 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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nmwsharp/polyscope
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 3/5 1-2 days Newbie friendliness 48/100
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
-
Rust Version Open
Difficulty 5/5 Over a week Newbie friendliness 15/100
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 20/100
All issues in nmwsharp/polyscope
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
flutter-webrtc/flutter-webrtc#2206 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
google-ai-edge/LiteRT-LM#3739 ·
-
Component: GLib
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
brave/brave-browser#59300 ·
-
Mute ydb/tests/functional/dstool/test_canonical_requests.py.Test.test_group_take_snapshot in main Openai_reviewed
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
ydb-platform/ydb#53974 · 3 comments ·