Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Paradrops
#5
Not everyone wants a single plane packed to the brim, and that goes against the original logic... I can't think of a way to enumerate multiple planes and contents short of Paradrop.Country.Plane1Units = , Paradrop.Country.Plane2Units = and so on, with Paradrop.Country.PlaneCount ... but that would be a real bitch to code and a lot of memory taken up. Though I'm pretty sure I can get rid of the two separate lists for units and counts internally, that still leaves
Code:
        countries  planes   units
Vector<   Vector<  Vector<  TechnoTypeClass*> > >
, which is rather crazy.

What about the suggestion in the issue I linked to, where you just define taskforces/teams to invoke instead of enumerating each plane, e.g. Country.Taskforces = a, b, c, d ; ? That would reduce internal storage to
Code:
       countries  teams
Vector<  Vector<  TeamTypeClass *> >
which is reasonably simpler. Though getting that to work will prove hard still...

Worth playing: 1 | 2 | 3
Reply


Messages In This Thread
Paradrops - by DCoder - 22.09.2008, 20:16:54
RE: Paradrops - by MRMIdAS - 22.09.2008, 20:31:46
RE: Paradrops - by Marshall - 22.09.2008, 20:42:50
RE: Paradrops - by TheMan - 22.09.2008, 21:12:42
RE: Paradrops - by DCoder - 22.09.2008, 22:22:02
RE: Paradrops - by 4StarGeneral - 23.09.2008, 14:47:12
RE: Paradrops - by Guest - 23.09.2008, 18:56:02
RE: Paradrops - by Marshall - 23.09.2008, 19:55:05
RE: Paradrops - by Nikademis Von Hisson - 10.11.2008, 06:00:21
RE: Paradrops - by mt. - 11.11.2008, 00:27:46
RE: Paradrops - by Guest - 02.10.2009, 09:17:30



Users browsing this thread: 1 Guest(s)