Rocks'n'Diamonds

This is a good question for my very first poll.

While the token "next_CE_1" is good for the reference element "self+1", "last_CE_1" is not as good for "self-1", so I propose "prev_CE_1", for quite obvious reasons

I think that this token has never been used in any configuration file yet (and hardly will be used in the future), so this change shouldn't break anything.

Hey, wait a moment, those reference elements' tokens shouldn't even be displayed!

Uh, just got the answer on my own: one could wish to customize the graphical buttons for them, so will use their tokens, okay.

Seen your votes, and counted them a bit (Yes: 4, No: 0) seems that the token should be renamed.

> so I propose "prev_CE_1", for quite obvious reasons

Hm. What's wrong with "last_CE_1"?

Just thought of "next" (self+1), "next but one" (self+2) and so on and "last" (self-1), "last but one" (self-2) and so on. Isn't this correct? At least it's not obvious to me that something could be wrong here... :-o

> I think that this token has never been used in any configuration file yet
> (and hardly will be used in the future), so this change shouldn't break
> anything.

That's right -- changing it should be no problem at all.

> Hey, wait a moment, those reference elements' tokens shouldn't even be
> displayed!

Well, it shouldn't hurt either... ;-)

Well, it is all about the fact that the antonym of "next" is "previous" and that the antonym of "last" is "first"

It doesn't really matter, but the poll results agree with the rename

> Hey, wait a moment, those reference elements' tokens shouldn't even be
> displayed!

Well, it shouldn't hurt either...

Mmm, did you miss the answer that I gave to myself?

Uh, just got the answer on my own: one could wish to customize the graphical buttons for them, so will use their tokens, okay.

> Well, it is all about the fact that the antonym of "next" is "previous" and
> that the antonym of "last" is "first"

Humm... Maybe you're right. :)

> It doesn't really matter, but the poll results agree with the rename

Well... to be honest, I would prefer one single vote of a native speaker over 10 votes of non-native speakers. ;-)

Any native English speaker around who reads this? Please advise! :-)

(Especially the "last but one", "last but two" etc. idioms from my dictionary gave me the impression that "last" could also be correct here... :-o )

> Mmm, did you miss the answer that I gave to myself?
[...]

No, I didn't! I totally agree with you (that it's not really needed at all)! :-)

I just meant that I didn't want to remove the token name from 1% of the element pages because it's not needed in a special case, but just keep it there anyway... ;-)

But yes, it *could* be used to customise the editor graphics... :-)

I don't think we need a native speaker here. Francesco is just right, it's clear enough!

Even though I'm not native english speaker, I got a (hopefully good) argument about why this should be changed:

http://dictionary.reference.com/search?q=last&x=0&y=0 wrote:1. occurring or coming after all others, as in time, order, or place: the last line on a page.
2. most recent; next before the present; latest: last week; last Friday.

A page is finite, the lines must end sooner or later. But no one knows how many weeks that will come, or how many fridays will be left in the world.
So that's why I'd say that it should be called "previous CE" and not "last CE", because "the last CE" - even though it could be related to self-1 - also can be meant as "the last CE left" (with the meaning that 255 CEs already has been used) or "the last CE" as in CE #256.

While "previous CE" (http://dictionary.reference.com/search? ... us&x=0&y=0) does not relate to CE #256.

OK, OK, you got me, I'm finally convinced! :-D ;-)

I'll change it in the next version.

Seems that I have to change some other tokens as well due to my misunderstanding, for example as in "last_level"/"next_level", which should then also be "previous_level". Oh well... ;-)

Holger wrote:Seems that I have to change some other tokens as well due to my misunderstanding, for example as in "last_level"/"next_level", which should then also be "previous_level". Oh well...

To be sincere I've never seen such tokens... in any case, you should do that only if you mean some generic "previous" and "next", related to a list. If "last_level" means "the last level that you have played", it should be left so.

It's the token "menu.button.last_level", to define a button image for decrementing the level counter. So it probably also should be "previous" here...

Probably also not too widely used...

Yes, that should be renamed.
But... isn't it used by all custom levelsets like Alan's ones?

Hope that rename won't break any graphic for existing levelsets, but you know your job, and most probably you will allow RnD recognize the old tokens as well.

Holger wrote:Any native English speaker around who reads this? Please advise!

Advising, please wait...
Dumping Output:
OK, I vote to change the name from "last" to "previous." It is less confusing.

Thanks! :-)
Done!