Shukant Pal
Shukant Pal
So the child problem is kind of why I didn't want to add a "default" way of implementing interactivity. Although @pixi-essentials/svg does provide a scene graph, it's a "disconnected" internal...
Yeah, since the prototype modification worked that doesn't seem necessary. I can add it to the documentation though.
The `.es.js` files are using ES6. Make sure you support ES6 or use the CommonJS build instead.
Or you might be able to configure Babel to run on the .es.js
Please add original svg element's IDs as name to children so we can use getChildByName()! (see code)
@bencresty The way I recommend you do it is override `populateSceneRecursive` and store the node created and associate it with the SVG element in a map :)
Please add original svg element's IDs as name to children so we can use getChildByName()! (see code)
> Is there anything against making this work the pixi-way by just adding that one line as mentioned? No, not really. Feel free to make a PR. I can publish...
Please add original svg element's IDs as name to children so we can use getChildByName()! (see code)
lol With the time you spent whining, the PR could've been made by now. /s You can press "." on the GitHub repo to open VS Code in the browser...
I'd be happy to accept a PR. Otherwise, we debug this when I have free time :)
The SVGScene is optimized for rendering speed. It doesn't have a _contains method by default for hit testing. However, setting a hitArea should definitely work. Can you create a minimal...
I think you can extend `SVGScene` and implement [containsPoint](https://api.pixijs.io/@pixi/graphics/PIXI/Graphics.html#containsPoint). ``` public containsPoint({ x, y }): void { return this.root.containsPoint(x, y) } ```