max-mapper / max-mapper/elementary-electron
Cat Annotation - issue with lightning-image-poly package
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 231
- Forks
- 43
- PR merge metrics
- No merged PRs in 30d
Description
Hi kind contributors
Thank you for the easy to follow guide to setting up electron app. Everything worked fine for me in this course except for the bug with the polygon drawing package
I could kinda draw squiggly lines after following the tutorial, but my doodling disappeared the moment I release my mouse. Also, my browser buffer size increase as if there were more elements added to it, which I think is what the code below was trying to do:
```
var viz = new image('#visualization',null,[src],{hullAlgorithm:'convex'});
```
Because there was a code that was supposed to delete the original image and re-render it, the new image was taking super long to render while the old image was not deleted either. And the drawing didn't seem to be at the right location.
Please kindly help explain what was going on.
My entire code was:
```
var picture=require('cat-picture');
var image=require("lightning-image-poly");
var src=picture.src;
picture.remove();
var viz = new image('#visualization',null,[src],{hullAlgorithm:'convex'});
```
Thank you
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.
Research direction
Start by reproducing the provided Electron code using cat-picture and lightning-image-poly, focusing on the image constructor and the mouse-release behavior described in the issue. Compare the rendered image, browser buffer growth, deletion timing, and drawing position with the tutorial's expected behavior. Done means the drawing persists in the intended location and the original image is replaced without excessive rendering delay.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100