Need some expert assistance on a complex situation (long po

Colen McAlister wrote:
> If you want the weapons to appear under every ship, you'll have to use
> items to model them.

I switched them all to items the day after I made that post. They look
much nicer that way anyway, since they now appear in italics and really
stand out from the other stats.

> The only way I can think of to do this is to define a hidden statistic,
> for the sake of argument called 'MaxSize'. Set the "Escort Squadron"
> unit to have a MaxSize of 6, and define a stat comparison using lcmp
> (unit external attribute) that makes sure that MaxSize is always >= 0.
> Then, have each of the child units (Iconoclasts, Infidels, etc etc)
> decrease the MaxSize of their parent (prnt option attribute, I think)
> by 1. Thus, if you ever have a negative MaxSize, there will be 7 or
> more models in the unit, making it illegal, and an appropriate
> validation message can be displayed.

I had found an earlier post made by you that said basically the same
thing for a problem that another user had. Why this doesn't work for
my case is that you must have 2-6 models in the parent unit, with
each model coming from up to 3 child units (Iconoclasts, Infidels and/
or Idolators). Each of these child units consists ~solely~ of models
of that type so you would never have 2 Iconoclast child units in the
same parent unit. The following are all valid selections:

##
Escort Squadron 1
+Iconoclast Class Destroyers+ 3
+Infidel Class Raiders+ 3
(1 squadron of 6 models from 2 types)


##
Escort Squadron 1
+Iconoclast Class Destroyers+ 3
(1 squadron of 3 models from 1 type)

##
Escort Squadron 1
+Iconoclast Class Destroyers+ 2
+Infidel Class Raiders+ 1
+Idolator Class Raiders+ 2
(1 squadron of 5 models from 3 types)

Per your suggestion, I would have to add 3 Iconoclast child units in
order to decrement the MaxSize stat, wouldn't I?

I thought about using the MaxSize stat with a 'rang' attribute so that
I could alter the stat per the number of times that option is selected
and still only have 1 child unit displayed with multiple models.
However, that still leaves the child unit open for the user to use the
standard '+/-' buttons which won't be connected to the validation and
as far as I know there's no way for these buttons to be disabled.

I have also thought about only having the child units appear in the
printed roster while they are purchased per the idea in the paragraph
above. This would solve the '+/-' problem, but I don't know of any way
to actually hide the child units in the interface but show them in the
printed roster.

Is there some way I could make the child units items instead and use
an element to combine them with their weapons items and track them
by item count in the parent unit?

Thanks for your time on this,
Randel

------------------------ Yahoo! Groups Sponsor ---------------------~-->
Buy Ink Cartridges or Refill Kits for Your HP, Epson, Canon or Lexmark
Printer at Myinks.com. Free s/h on orders $50 or more to the US & Canada. http://www.c1tracking.com/l.asp?cid=5511
http://us.click.yahoo.com/l.m7sD/LId...sNAA/IMSolB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, email

armybuilder-unsubscribe@yahoogroups.com

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/

[Colen]

At 11:13 AM 8/28/2003 +0200, you wrote:



> > The only way I can think of to do this is to define a hidden statistic,
> > for the sake of argument called 'MaxSize'. Set the "Escort Squadron"
> > unit to have a MaxSize of 6, and define a stat comparison using lcmp
> > (unit external attribute) that makes sure that MaxSize is always >= 0.
> > Then, have each of the child units (Iconoclasts, Infidels, etc etc)
> > decrease the MaxSize of their parent (prnt option attribute, I think)
> > by 1. Thus, if you ever have a negative MaxSize, there will be 7 or
> > more models in the unit, making it illegal, and an appropriate
> > validation message can be displayed.
>
>I had found an earlier post made by you that said basically the same
>thing for a problem that another user had. Why this doesn't work for
>my case is that you must have 2-6 models in the parent unit, with
>each model coming from up to 3 child units (Iconoclasts, Infidels and/
>or Idolators). Each of these child units consists ~solely~ of models
>of that type so you would never have 2 Iconoclast child units in the
>same parent unit.
>
>Per your suggestion, I would have to add 3 Iconoclast child units in
>order to decrement the MaxSize stat, wouldn't I?

Use an expression to subtract the current unit size from the stat of the
parent unit. For example:

prnt:MaxSize+(#)

Sorry I wasn't more clear on this earlier.


--
Colen McAlister (colen@wolflair.com)
Lone Wolf Development www.wolflair.com



------------------------ Yahoo! Groups Sponsor ---------------------~-->
Buy Ink Cartridges or Refill Kits for Your HP, Epson, Canon or Lexmark
Printer at Myinks.com. Free s/h on orders $50 or more to the US & Canada. http://www.c1tracking.com/l.asp?cid=5511
http://us.click.yahoo.com/l.m7sD/LId...sNAA/IMSolB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, email

armybuilder-unsubscribe@yahoogroups.com

Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/