[HELP] Blanks can only be added after items.
Fixed
|
Re: [HELP] Blanks can only be added after items.
Your loops, where you add blank and the items, are wrong. And the compiler says it itself.
|
Re: [HELP] Blanks can only be added after items.
You always have to add an item first before adding a blank using menu_addblank. The code you have provided should not trigger this behavior since you always use menu_additem first before reaching menu_addblank.
|
Re: [HELP] Blanks can only be added after items.
Quote:
Quote:
menu_additem and blank Can you answer my questions - 192 characters |
Re: [HELP] Blanks can only be added after items.
You.don't really need 192. That's too many. Simply explained - this shows how many characters can you have in your string (inthat case)(it could be array also). Usually, you may use 32 or 64 for titles.
|
Re: [HELP] Blanks can only be added after items.
Quote:
|
Re: [HELP] Blanks can only be added after items.
How will I know how to set up?
50 It is good to this menu? |
Re: [HELP] Blanks can only be added after items.
Yes. You have to understand one: the size you put in these brackets after the variable defines how many letters could there be in this string (in that case it is the menu title). If you won't use more than 63, you can put 64. These numbers like 32, 64, 128, etc., are mostly used, because hey are multiples of 2 (it's a principle in the programming).
|
Re: [HELP] Blanks can only be added after items.
Oh it is based on the amount of letters.
Code:
formatex( szMenu, charsmax( szMenu ), "\r[%s] \yShop Main Menu^n\wYou have \y%i \wcash"Code:
static szMenu[ 64 ]Has been explained to me the other day, but for you what is useful for me here on the menu? |
Re: [HELP] Blanks can only be added after items.
The menu does not care about what your variable is, it just cares about what string is inside it. It doesn't care wether the variable is declared new or static. Static is not needed for this function.
|
| All times are GMT -4. The time now is 21:05. |
Powered by vBulletin®
Copyright ©2000 - 2024, vBulletin Solutions, Inc.