Digest Number 490

------------------------ Yahoo! Groups Sponsor ---------------------~-->
Win a Marvel vs. CapCom 2 Arcade System!
Click Here to Enter...
http://us.click.yahoo.com/9YX7sC/o58...uFAA/IMSolB/TM
---------------------------------------------------------------------~->

To unsubscribe from this group, email

armybuilder-unsubscribe@egroups.com
------------------------------------------------------------------------

There are 7 messages in this issue.

Topics in this digest:

1. Making an item available based on presence of a unit
From: jizbrand@kc.rr.com
2. Re: Making an item available based on presence of a unit
From: Rob Bowes <rob@wolflair.com>
3. Re: Making an item available based on presence of a unit
From: Rob Bowes <rob@wolflair.com>
4. Re: Making an item available based on presence of a unit
From: jizbrand@kc.rr.com
5. Re: Making an item available based on presence of a unit - last time!
From: jizbrand@kc.rr.com
6. Re: Making an item available based on presence of a unit
From: jizbrand@kc.rr.com
7. Re: Making an item available based on presence of a unit - last time!
From: Rob Bowes <rob@wolflair.com>


__________________________________________________ ______________________
__________________________________________________ ______________________

Message: 1
Date: Sun, 26 Aug 2001 23:56:14 -0000
From: jizbrand@kc.rr.com
Subject: Making an item available based on presence of a unit

Rats!!! Just when I thought I was getting the hand of this . . .

In my race special attributes I have:
need:unit=UnitA@1m-item=ItemA

I have a UnitA defined under units, and ItemA defined under items.

What I think the "need" statement is saying is that I have to have 1
model of UnitA for each ItemA I want to include in the list.

Unfortunately, AB will cheerfully let me have all the ItemAs I want
without having even one UnitA in the list. What am I missing?



__________________________________________________ ______________________
__________________________________________________ ______________________

Message: 2
Date: Sun, 26 Aug 2001 19:24:07 -0700
From: Rob Bowes <rob@wolflair.com>
Subject: Re: Making an item available based on presence of a unit

The "need" attribute dictates that you must have a UNIT present in your
roster. If you specify an item, then the unit is only required IF you have
taken that item. This is the completely wrong attribute if you are trying
to control the selection of items, since it governs UNITS.

What exactly are you trying to accomplish? If you need to require that the
selection of ItemA also forces the user to select UnitA, then you need to
use a completely different approach. This is solved by having ItemA use the
"type" attribute to assign the type "ItemA" to the unit carrying it. Then
use the "type" attribute to assign "UnitA" to the necessary unit. To verify
compliance, use the "trat" attribute to confirm that the presence of type
"ItemA" requires type "UnitA" to be in the roster. You can control the
"trat" attribute to verify a 1:1 ratio, an open-ended requirement, or just
about any other relationship.

Hope this helps,
Rob


At 11:56 PM 8/26/2001 +0000, you wrote:
>Rats!!! Just when I thought I was getting the hand of this . . .
>
>In my race special attributes I have:
> need:unit=UnitA@1m-item=ItemA
>
>I have a UnitA defined under units, and ItemA defined under items.
>
>What I think the "need" statement is saying is that I have to have 1
>model of UnitA for each ItemA I want to include in the list.
>
>Unfortunately, AB will cheerfully let me have all the ItemAs I want
>without having even one UnitA in the list. What am I missing?


---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (650) 726-9689
Lone Wolf Development www.wolflair.com



__________________________________________________ ______________________
__________________________________________________ ______________________

Message: 3
Date: Sun, 26 Aug 2001 19:24:07 -0700
From: Rob Bowes <rob@wolflair.com>
Subject: Re: Making an item available based on presence of a unit

The "need" attribute dictates that you must have a UNIT present in your
roster. If you specify an item, then the unit is only required IF you have
taken that item. This is the completely wrong attribute if you are trying
to control the selection of items, since it governs UNITS.

What exactly are you trying to accomplish? If you need to require that the
selection of ItemA also forces the user to select UnitA, then you need to
use a completely different approach. This is solved by having ItemA use the
"type" attribute to assign the type "ItemA" to the unit carrying it. Then
use the "type" attribute to assign "UnitA" to the necessary unit. To verify
compliance, use the "trat" attribute to confirm that the presence of type
"ItemA" requires type "UnitA" to be in the roster. You can control the
"trat" attribute to verify a 1:1 ratio, an open-ended requirement, or just
about any other relationship.

Hope this helps,
Rob


At 11:56 PM 8/26/2001 +0000, you wrote:
>Rats!!! Just when I thought I was getting the hand of this . . .
>
>In my race special attributes I have:
> need:unit=UnitA@1m-item=ItemA
>
>I have a UnitA defined under units, and ItemA defined under items.
>
>What I think the "need" statement is saying is that I have to have 1
>model of UnitA for each ItemA I want to include in the list.
>
>Unfortunately, AB will cheerfully let me have all the ItemAs I want
>without having even one UnitA in the list. What am I missing?


---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (650) 726-9689
Lone Wolf Development www.wolflair.com



__________________________________________________ ______________________
__________________________________________________ ______________________

Message: 4
Date: Mon, 27 Aug 2001 02:41:26 -0000
From: jizbrand@kc.rr.com
Subject: Re: Making an item available based on presence of a unit

Oh, one other detail: when UnitA is included in the roster, ItemA
should be a selectable option for units other than UnitA.




__________________________________________________ ______________________
__________________________________________________ ______________________

Message: 5
Date: Mon, 27 Aug 2001 02:49:24 -0000
From: jizbrand@kc.rr.com
Subject: Re: Making an item available based on presence of a unit - last time!

Okay, I have a solution (not the more elegant one I wanted, but it
works). I have ItemA selectable in the items list. Selecting
confers type:HasItemA on the unit that takes it. UnitA has
type:AllowsItemA. In the racial attributes, I have a trat:AllowsItemA
(at)1m:HasItemA(at)1m.

That triggers the validation error which is good enough. Thanks.




__________________________________________________ ______________________
__________________________________________________ ______________________

Message: 6
Date: Mon, 27 Aug 2001 02:30:18 -0000
From: jizbrand@kc.rr.com
Subject: Re: Making an item available based on presence of a unit

Actually, I think I'm doing the opposite. I don't want the item to
even show up as selectable until the unit has been added to the
roster. I thought about doing it the opposite way -- having
selection of the item trigger the addition of the unit (which I did
with a different item), but the flow of roster design, in this case,
should be that the unit is added and that opens up other items. So
what I need to do is, instead of forcing selection, have selection of
UnitA enable the optional selection of ItemA, not the forced
selection of either. Clear as mud?

From: Rob Bowes <rob@w...>
Date: Mon Aug 27, 2001 2:24 am
Subject: Re: [AB] Making an item available based on presence of a
unit


The "need" attribute dictates that you must have a UNIT present in
your
roster. If you specify an item, then the unit is only required IF you
have
taken that item. This is the completely wrong attribute if you are
trying
to control the selection of items, since it governs UNITS.

What exactly are you trying to accomplish? If you need to require
that the
selection of ItemA also forces the user to select UnitA, then you
need to
use a completely different approach. This is solved by having ItemA
use the
"type" attribute to assign the type "ItemA" to the unit carrying it.
Then
use the "type" attribute to assign "UnitA" to the necessary unit. To
verify
compliance, use the "trat" attribute to confirm that the presence of
type
"ItemA" requires type "UnitA" to be in the roster. You can control
the
"trat" attribute to verify a 1:1 ratio, an open-ended requirement, or
just
about any other relationship.

Hope this helps,
Rob


At 11:56 PM 8/26/2001 +0000, you wrote:
>Rats!!! Just when I thought I was getting the hand of this . . .
>
>In my race special attributes I have:
> need:unit=UnitA@1...=ItemA
>
>I have a UnitA defined under units, and ItemA defined under items.
>
>What I think the "need" statement is saying is that I have to have 1
>model of UnitA for each ItemA I want to include in the list.
>
>Unfortunately, AB will cheerfully let me have all the ItemAs I want
>without having even one UnitA in the list. What am I missing?









__________________________________________________ ______________________
__________________________________________________ ______________________

Message: 7
Date: Mon, 27 Aug 2001 00:53:07 -0700
From: Rob Bowes <rob@wolflair.com>
Subject: Re: Making an item available based on presence of a unit - last time!

And you can assign an "itst" attribute to ItemA that makes the item not
selectable for UnitA (per your second post of the three that came in a
flurry). :-)

Glad you got it figured out....

Thanks, Rob


At 02:49 AM 8/27/2001 +0000, you wrote:
>Okay, I have a solution (not the more elegant one I wanted, but it
>works). I have ItemA selectable in the items list. Selecting
>confers type:HasItemA on the unit that takes it. UnitA has
>type:AllowsItemA. In the racial attributes, I have a trat:AllowsItemA
>(at)1m:HasItemA(at)1m.
>
>That triggers the validation error which is good enough. Thanks.


---------------------------------------------------------------------------
Rob Bowes (rob@wolflair.com) (650) 726-9689
Lone Wolf Development www.wolflair.com



__________________________________________________ ______________________
__________________________________________________ ______________________



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