One nice thing about the GYFM exports is that it's pretty easy to tack on special chars or edit chars; just bring the spritefont into gimp and set the grid size to the height/width specified. Drop the char(s) you need into a blank spot, then plug the char(s) into the JSON 'letterset' string and specify it's width (the measure tool in gimp works for that).

> What you are suggesting indeed fails. I think what Ashley was talking about was having constant strings that point to your functions.

>

> Then, if you changed the name of a function, the only place you would have to update the value would be in the corresponding constant, which could be referenced elsewhere in your code. You would only have to do this for functions that were going to be called in multiple places.

>

> However, now that I think about it, I don't see why we should be prevented from naming functions with constant global strings...it's not like they are going to change.

>

> Ashley ???

>

Actually, it seems to be due to the implémentation of functions themselves, where each "on function" issue a totally different call (when you call a function, it will not test each function's name then execute, it will only trigger directly said function), that however needs a direct name for the function.

But...a constant global string won't change. Right?

Still, I can see the complications of this, most of which would be edittime issues:

1. What if you change a var from constant to non-constant? What do you do for functions 'named' by that var? Invalidate them? Delete them? 2. What if you create a function called "Foo" and name another function after a constant with the value "Foo"...is the editor supposed to sort all that out?

I guess that's the thing about a lot of 'simple' requests: implementing them is rarely as easy as it seems.

This project is starting to look really good. I love the metroidvania genre. Can't wait to see your first boss in action...

What you are suggesting indeed fails. I think what Ashley was talking about was having constant strings that point to your functions.

Then, if you changed the name of a function, the only place you would have to update the value would be in the corresponding constant, which could be referenced elsewhere in your code. You would only have to do this for functions that were going to be called in multiple places.

However, now that I think about it, I don't see why we should be prevented from naming functions with constant global strings...it's not like they are going to change.

Ashley ???

Colludium

So, you're having a couple special chars that are displaying in GYFM, but aren't being exported to the font-sheet or listed in the JSON? If so, have you tried exporting them separately?

Congrats! Hopefully the first in a long line of hits.

Here's something I put together on a lark. Warning: this is a total impractical effect; it's a modification of a project I created for the sole purpose of maxing out the fill rate on my computer to see what would happen...

[attachment=0:ykc7eq7r][/attachment:ykc7eq7r]

yonda

Your example looks great...but it's herky jerky for me...

Depends on how you are 'scrolling'. Capx?

Glad I could help...good luck with your project.

I...don't understand this

Do you want to get the name of the current layout and store it in a variable? If so: