Well, if you don't mind 3rd party plugins, Pode HTML Pack comes to mind, especially the DIV plugin.
Otherwise, maybe you could use a disabled text-area and fiddle with its CSS so it looks like a simple rectangle.
CSS is used to style DOM elements. Sprites and Text objects both aren't DOM element, so tough luck I guess.
Develop games in your browser. Powerful, performant & highly capable.
Check if the seamless mode is turned on in the tilemap's properties. Also, having the project's property "sampling" set to "point" can help too.
The OR works, however the SOL is devoid of any "Player", so no "Player" action can occur.
Since you probably have only one player, I guess you could add a subevent with a "Pick all Player", and put your action in there.
Like this :
The following regular expression will match positions which need a comma inserted.
(\d)(?=(\d{3})+$)[/code:f0idjxqc] So the following RegexReplace should do the trick : [code:f0idjxqc]RegexReplace(str(value), "(\d)(?=(\d{3})+$)", "g", "$1,")[/code:f0idjxqc] Note that it will only work with integers.
If used, the "trigger once" pseudo-trigger should always be used as the last condition. It's explicitely specified in the manual.
Does RegexReplace... work with Sprite Fonts? Of course it does. It's a text function, it works with anything string related.
Does RegexReplace... work with Sprite Fonts?
Of course it does. It's a text function, it works with anything string related.
Unfortunately no. The whole plugin rely on the EasyStarJS library which is an A* pathfinding algorithm javascript implementation.
Project's property "Sampling" must be set to "Point". Better result with integer scale too.
Well to be fair, it's one of the most content heavy page in the manual. It's easy to start skimming and accidently skip a line.
It's far from hard. Here:
replace(src, find, rep) Find all occurrences of find in src and replace them with rep.
replace(src, find, rep)
Find all occurrences of find in src and replace them with rep.
Move the "Node -> Destroy" action from line 2 down to line 3.
This example was created with a previous version of EasyStarJS. The asynchronous aspect of the plugin changed in a way that made the node sprite get destroyed AFTER they were created (in the same tick), so it was never visible. You could also only change the "asynchronous" property to "no", and the node sprites would appear again.
Member since 4 Jul, 2011