Thanks everyone. A lot of good info here.
Note for people trying to use the arrays; if you plan on using the array to store numeric values instead of text, make sure that's reflected in the array properties or you'll tear your hair out trying to get the array to store and display your written values ;D
to jarred, late reply: i thought you already had the available weapons stored somewhere, flags on an object would make sense, just put on flag 1,2,3,4,5 when you get a weapon, and use the event internal flag currentweapon is on/off.
i would use two different values for currentweapon to be safe, one to fire the events i mentioned and one to actually give you the selected weapon (when you know the flag is on) or use Chrille's version which is probably the best one ;)
i am skeptical of lists since it's a big string of text, but maybe it's faster than i think it is.
Hi. You shouldn't be skeptical of List Objects because you think they are slow. Easier to use in this case than Arrays.
Marv
Since the original post asked that the weapons be in a predefined order, how are you manipulating the List object so that as you pick up new weapons they are added to the list in the proper order? Sorry, I haven't checked out the sample file yet, but are you keeping a set of events that is hardcoded to insert the weapon into the right spot in the List?
Interesting thread,
add some thoughts about latest clever observations:
1) to properly decide you should clarify whether:
a) you need to store your weapons in predetermined order or not
b) you need this system to support multiple players
c) you need to store (and save?) other values/infos about those weapons or just their availability (ex. ammo count, powerup level...)
d) you need to store/save additional data about your game (...that could all be packed in a differently setup array)
2) as for list speed, some time ago I tested list objects + fastloops for a random map generation,
and that was hugely slower than same setup based on array + fastloops (about 2 seconds vs 0).
But that was a large project building up hundreds of cells,
so I'd say for small scale and few steps at a time it's surely fast enough.
For my purposes, the array is awesome. I know I'm going to use them a lot and this was a really good exercise to reintroduce them to me. The only thing I'm dreading is creating referential diagrams on paper to keep track of what means what at each dimension...but still incredibly useful.
I admittedly have never tested the "internal list object" that by definition is a "faster list object" :)
so I have no actual speed comparisons to report on that
(side note: I see it's windows only, don't know if viable for Jarred?)
As for my tests I would clarify that I was talking about standard "list object",
as the one used in the examples posted,
and I agree that it would better (cleaner & easier to setup) suit these singular weapon scrolling needs in comparison to an array,
even if slower (I guess because, differently from the "internal list", it is sort of a "GUI" object and has to show the highlight moving etc.)
(.....although I have a love affair with arrays so I can't question anyone choosing that way XDXD)
Given this warm endorsing by Snail, I will for sure test internal list on future plans, seems a really interesting thing :)
EDIT: knowing about internal list speed before I would have never tested a simple "list object" against an array for my purposes... well, next time!
Eh, I'm developing on Windows but hope to do ports to the other platforms (of course no mouse movement there). Arrays just always seemed to be the most logical way to set up info to me. Plus I want to control 'upgrade' type additions so the array let's me keep that nice and tidy :) I'm already on a 5x5 grid and reworking my code to poll the info from the array (which will make future updates and changes a breeze :) )Quote:
Originally Posted by schrodinger
Good to know about the lists tho. If I notice sluggishness it's good to know there are options to make things speedier.