processing / processing/p5.js-web-editor
loadImage file path acting up, loads with arbitrary folder names.
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.7k
- Forks
- 1.7k
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 8
Description
- [ x] Found a bug
When I run this locally, everything works as expected.
One of my students ran into this problem and I have been able to reproduce it, only with his sketch. I wrote a version previously as an example and it runs fine, not sure why it's the case with his. I have even started from scratch as a new sketch and ended with the same result when I use his images. ...
Something is making loadImage() point to the same file path resulting in all my image calls drawing the same image sequence. The weird thing is, I can put in a path that doesn't exist and it still draws the images. It does break if I don't have the image named correctly ...
for example ...
'images/uhh/frame_' ... defaults to the first folder inside images folder. fyi, uhh an arbitrary folder name, it is not a folder or anything that exists in this project.
sketch is provided below.
70.0.3538.77 (Official Build) (64-bit)
Revision | 0f6ce0b0cd63a12cb4eccea3637b1bc9a29148d9-refs/branch-heads/3538@{#1039}
OS | Mac OS X
Same result in firefox, sierra, both Mac and Windows
Contributor guide
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.
Research direction
Start by reproducing the linked sketch and inspect how its loadImage() calls resolve image paths, especially the nonexistent 'images/uhh/frame_' prefix. Confirm the behavior across the reported browsers and verify that nonexistent folder names no longer cause all image calls to load the same image sequence.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100