error 047: array sizes do not match, or destination array is too small - Printable Version

+- SA-MP Forums Archive (https://sampforum.blast.hk)
+-- Forum: SA-MP Scripting and Plugins (https://sampforum.blast.hk/forumdisplay.php?fid=8)
+--- Forum: Scripting Help (https://sampforum.blast.hk/forumdisplay.php?fid=12)
+--- Thread: error 047: array sizes do not match, or destination array is too small (/showthread.php?tid=654314)

---

error 047: array sizes do not match, or destination array is too small - PizzaMag - 26.05.2018

I tried every single way around this error, it just doesn't want to work. I am trying to save a hex string in an array but whenever I do so, it gives me this error: error 047: array sizes do not match, or destination array is too small

The array in the enum is exactly same as in the command. Here is the observable code:

and the command:
and the errors I am getting:

---

Re: error 047: array sizes do not match, or destination array is too small - Sew_Sumi - 26.05.2018

I'm just going to say, there'll be a better way of doing this.

Such as defining the chat colors, and simply using the chat callback to check for their status and format the text itself without storing the individual colors in the enums for the player.


Use the enums color selection as a setting, check that, and format the message accordingly based on that result.



While what I say 'avoids the issue', I really do think that later on, this approach that you've taken, would lead to problems.

The only reason I would continue going down this path you've taken, is if you were going to have custom color options for the chat.

Being these are static colors, there's no real reason to be running them in the enum itself.

---

Re: error 047: array sizes do not match, or destination array is too small - PizzaMag - 26.05.2018

That's not the idea I am trying to make. I am making a donor system whereas this level (5), you can select a custom color and and that color you selected has its own chat color.

Correct me if I didn't answer your question accordingly.

EDIT: This is what I am trying to do:
you use "/changecolor red" for example. when you type in the chat, the color would be something like this:
"Mag (0): Test".

So I am trying to store the color manually when you execute the command, when I try to define the colors with #define, this is what I get:

Error:

---

Re: error 047: array sizes do not match, or destination array is too small - Sew_Sumi - 26.05.2018

It wasn't a question, it was all a statement.

You need to shift from storing the color in the enum, and use it simply as a value, to use as a setting, and when you are trying to do that one format, use that setting to bring out the right format using a case check.


As I said, the idea of doing it this way, unless you are making allowance for custom enter-able colors, is only going to give you more headaches.

---

Re: error 047: array sizes do not match, or destination array is too small - PizzaMag - 26.05.2018

I honestly cannot seem to understand your statement, what do you mean by value and setting?

What do I exactly put in the /changecolor command and how do I retrieve the color chosen to be used in OnPlayerText?

---

Re: error 047: array sizes do not match, or destination array is too small - Sew_Sumi - 26.05.2018

Rather than storing the color as an rgb value, and trying to insert it into the text as hex, simply make the color value, a setting, an integer, so it goes 1 2 3 4 - 2174664 and you simply use those settings to check which color to format within a case statement.


If you then expand the system more, you could make a function to make that preformat the line so it doesn't need to be done a whole heap of times in the script itself.

In the current scenario of 4 colors, you'd only have it check on the OnPlayerText callback, but if you added more features, such as a car material text that used the same formatting, or a 3dtext, or something other than the onplayertext then you'd look at a function.



Probably to cut the error, all you'd need to do is make color[7], but as I've been mentioning, it's not such a good idea unless you are doing custom colors via RGB selection/text entry.


I also edit a lot, so re-read and refresh what I've put up.




ANNNNNDDD, a real good mess about to check out new methods, is to use a fresh new.pwn, and put the basics of what you need, in there, and see what you can produce.

---

Re: error 047: array sizes do not match, or destination array is too small - XXpro - 26.05.2018

put this
#define ff0000

---

Re: error 047: array sizes do not match, or destination array is too small - Sew_Sumi - 26.05.2018

Fix it properly and make your script more capable for the future.


And it's encouraging to see you try this...

and if you used this, set your defines to

And use case on pinfo[playerid][color] checking for the color, and formatting in that result where it's checked on the area you're formatting the text and displaying it.


This last portion, is what you'd look at putting in a function if you used it in more scenarios.



And, color in this instance wouldn't need to be the array... It'll simply be color.

---

Re: error 047: array sizes do not match, or destination array is too small - PizzaMag - 26.05.2018

I actually fixed it where I just made it the opposite, this is how I fixed it:

command:
OnPlayerText:
Even though this is a little bit lazy work, I can still put the colors in a dialog and there wouldn't be any error occuring for false color.

However, thank you for your help, Sew_Sumi. I kind of reformed what you suggested

---