This is awesome progress!
While experimenting with the webView2 addons I realized it's a bit painful to test the specific features. It would be cool if we could get a remote preview webView2 app we can use, similar to NW.js.
I created a similar effect that supports webGPU:
https://www.construct.net/en/make-games/addons/1103/add-color
(this is not a port this is a different effect with a different ID and uses a color variable)
I created a similar effect, it does the same plus a lot more and additionally supports webGPU.
You might want to check it out if you are looking for an alternative.
https://www.construct.net/en/make-games/addons/1107/gradient
Thank you Ashley, that would be greatly appreciated!
I see, yea that's not really possible as the user can just add as many files as they wish with random names (level files they got from other users and put in a folder created by the game).
I hope listing files could come as an additional feature!
Still seems to work well for basic save systems!
I love the new additions but:
I'm trying to port a nwjs file system to the new webView2 one, I immediately noticed one issue:
There is no way to list all files at a path, this is important as in the project the users can put files into a folder (for sharing custom levels) and I populate a menu with all the levels.
Is there a way to do this?
amazing stuff for webView2 I love it!
No this is an issue jeFawk reported.
Though in theory this could be used to always return false in "is tween "tag" playing" if the tween behavior is not ticking instead of starting to check for running tweens! Might be a simple improvement Diego could do as it would just be a simple if else.
Dynamic Layers and inactive Tween improvement are great additions!
awesome to see a new face doing Shaders for Construct 3!
Another amazing update!
I love the text icon, internalization and animation tags, makes my increased salt level taste a bit sweeter. xD
that's a quick stable!
Not complaining though, as I guess this means no month of just bug fix releases.
oh yea, that works, my bad!
Improvement for the amazing text tag system:
new condition `has any tag at position` (or a symbol like -1 we can use for any tag)
and a expression like `text.currentTag` that returns the tag in that event.
This would allow us to create one event that handles multiple tags, for tooltips etc. Currently we would need to create a new event per tag (or loop over a list).
btw is there a reason random UID isn't the default now? I don't see any downsides, so to me it makes sense as default to avoid some merge conflicts even if people forgot to set it.
Member since 6 Jul, 2017