Inquiry About Enabling GL_REPEAT in Polyscope (Python Version)
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
- Domain
- computer-graphics
Research direction
The issue names no files, tests, or entry points. Start by checking Polyscope's Python texture-mapping API for an existing GL_REPEAT option. Done means confirming whether the option exists or documenting a concrete support decision.
Written by the indexing model from the issue text.
Description
Dear Dr. Sharp,
I hope this message finds you well.
In my current project, I am working with UV coordinates that exceed the range [0, 1]. To handle this, I would like to enable the GL_REPEAT functionality for texture mapping. However, I noticed that Polyscope does not seem to support GL_REPEAT by default.
I am writing to ask whether there is an existing function in Polyscope (Python version) that allows enabling GL_REPEAT. If not, I would like to know whether support for this feature is planned for future releases.
Thank you for your time and for developing such a useful visualization tool. I look forward to your response.
Best regards,
Yulin
- 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 86/100
-
Sensor initialization takes very long when `--initial-sim-time` is set to current UNIX timestamp Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
gazebosim/gz-sensors#662 · 1 comment ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
comp-datalake
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ClickHouse/ClickHouse#121222 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
LadybirdBrowser/ladybird#12123 ·