A
armybuilder at yahoogroup
Guest
------------------------ Yahoo! Groups Sponsor ---------------------~-->
Buy Stock for $4
and no minimums.
FREE Money 2002.
http://us.click.yahoo.com/orkH0C/n97DAA/ySSFAA/IMSolB/TM
---------------------------------------------------------------------~->
To unsubscribe from this group, email
armybuilder-unsubscribe@egroups.com
------------------------------------------------------------------------
There are 4 messages in this issue.
Topics in this digest:
1. Attaching items to child units
From: "Simon Day" <scbd@btopenworld.com>
2. Re: Attaching items to child units
From: "Keith" <mobo@adelphia.net>
3. Re: Attaching items to child units
From: "rjsoz" <rjs@inorbit.com>
4. RE: Attaching items to child units
From: "Day, Simon" <simon.day@capitafhe.co.uk>
________________________________________________________________________
________________________________________________________________________
Message: 1
Date: Sun, 14 Apr 2002 21:55:56 +0100
From: "Simon Day" <scbd@btopenworld.com>
Subject: Attaching items to child units
Hi,
I have come across an interesting problem and was wondering if I am going quietly mad or if there is a way round it.
I have a main unit (Infantry Battalion) which is linked to several child units (HQ, gun company, etc) via an option - this works fine. Because I do not want the child units to be selectable individually, I have added the 'x' to the front of their unique id.
Since I also want the child units to start off with certain items, I have linked these to the specific child units via options and the 'take' syntax.
When running the resulting file within Army builder, the defaulted items are not allocated to the child units, nor am I able to assign the items manually (I get the 'Cannot currently be given any items' message). The parent and each child unit has the number of allowed items set to 9999.
If, however, I return to the creator package and remove the 'x' from the unique id on the child units, then my items are included on the child units when I pick the parent unit (excellent), but the child units are also selectable individually within the system (not so excellent).
Anyone know of a way round this ?
(I'm running version 2.2c)
Cheers,
Simon.
[Non-text portions of this message have been removed]
________________________________________________________________________
________________________________________________________________________
Message: 2
Date: Sun, 14 Apr 2002 22:00:20 -0600
From: "Keith" <mobo@adelphia.net>
Subject: Re: Attaching items to child units
If you add the Ex. attribute "hide" to the child units, that should remove them form the list of units at the top of AB. The user will never be able to select those child units unless another unit gives them the option to select them. Hope this helps.
Thanks,
Keith
----- Original Message -----
From: Simon Day
To: Army Builder List
Sent: Sunday, April 14, 2002 2:55 PM
Subject: [AB] Attaching items to child units
Hi,
I have come across an interesting problem and was wondering if I am going quietly mad or if there is a way round it.
I have a main unit (Infantry Battalion) which is linked to several child units (HQ, gun company, etc) via an option - this works fine. Because I do not want the child units to be selectable individually, I have added the 'x' to the front of their unique id.
Since I also want the child units to start off with certain items, I have linked these to the specific child units via options and the 'take' syntax.
When running the resulting file within Army builder, the defaulted items are not allocated to the child units, nor am I able to assign the items manually (I get the 'Cannot currently be given any items' message). The parent and each child unit has the number of allowed items set to 9999.
If, however, I return to the creator package and remove the 'x' from the unique id on the child units, then my items are included on the child units when I pick the parent unit (excellent), but the child units are also selectable individually within the system (not so excellent).
Anyone know of a way round this ?
(I'm running version 2.2c)
Cheers,
Simon.
[Non-text portions of this message have been removed]
Yahoo! Groups Sponsor
ADVERTISEMENT
To unsubscribe from this group, email
armybuilder-unsubscribe@egroups.com
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
[Non-text portions of this message have been removed]
________________________________________________________________________
________________________________________________________________________
Message: 3
Date: Mon, 15 Apr 2002 06:44:14 -0000
From: "rjsoz" <rjs@inorbit.com>
Subject: Re: Attaching items to child units
It is docuemnted that units without a valid race prefix (ie.
starting with x) cannot take items. As Keith suggested, use the hide
attribute.
Cheers,
Russell.
--- In armybuilder@y..., "Keith" <mobo@a...> wrote:
> If you add the Ex. attribute "hide" to the child units, that
should remove them form the list of units at the top of AB. The
user will never be able to select those child units unless another
unit gives them the option to select them. Hope this helps.
>
> ----- Original Message -----
> From: Simon Day
> To: Army Builder List
> Sent: Sunday, April 14, 2002 2:55 PM
> Subject: [AB] Attaching items to child units
>
>
> Hi,
>
> I have come across an interesting problem and was wondering if I
am going quietly mad or if there is a way round it.
>
> I have a main unit (Infantry Battalion) which is linked to
several child units (HQ, gun company, etc) via an option - this
works fine. Because I do not want the child units to be selectable
individually, I have added the 'x' to the front of their unique id.
>
> Since I also want the child units to start off with certain
items, I have linked these to the specific child units via options
and the 'take' syntax.
>
________________________________________________________________________
________________________________________________________________________
Message: 4
Date: Mon, 15 Apr 2002 07:53:43 +0100
From: "Day, Simon" <simon.day@capitafhe.co.uk>
Subject: RE: Attaching items to child units
Thanks guys - I'll give that a try.
Cheers,
Simon Day
> -----Original Message-----
> From: rjsoz [SMTP:rjs@inorbit.com]
> Sent: 15 April 2002 07:44
> To: armybuilder@yahoogroups.com
> Subject: Re: [AB] Attaching items to child units
>
> It is docuemnted that units without a valid race prefix (ie.
> starting with x) cannot take items. As Keith suggested, use the hide
> attribute.
>
> Cheers,
> Russell.
>
> --- In armybuilder@y..., "Keith" <mobo@a...> wrote:
> > If you add the Ex. attribute "hide" to the child units, that
> should remove them form the list of units at the top of AB. The
> user will never be able to select those child units unless another
> unit gives them the option to select them. Hope this helps.
> >
> > ----- Original Message -----
> > From: Simon Day
> > To: Army Builder List
> > Sent: Sunday, April 14, 2002 2:55 PM
> > Subject: [AB] Attaching items to child units
> >
> >
> > Hi,
> >
> > I have come across an interesting problem and was wondering if I
> am going quietly mad or if there is a way round it.
> >
> > I have a main unit (Infantry Battalion) which is linked to
> several child units (HQ, gun company, etc) via an option - this
> works fine. Because I do not want the child units to be selectable
> individually, I have added the 'x' to the front of their unique id.
> >
> > Since I also want the child units to start off with certain
> items, I have linked these to the specific child units via options
> and the 'take' syntax.
> >
>
>
>
>
> To unsubscribe from this group, email
>
> armybuilder-unsubscribe@egroups.com
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
> ________________________________________________________________________
> This email has been scanned for all viruses by the MessageLabs SkyScan
> service. For more information on a proactive anti-virus service working
> around the clock, around the globe, visit http://www.messagelabs.com
> ________________________________________________________________________
________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service. For more information on a proactive anti-virus service working
around the clock, around the globe, visit http://www.messagelabs.com
________________________________________________________________________
________________________________________________________________________
________________________________________________________________________
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Buy Stock for $4
and no minimums.
FREE Money 2002.
http://us.click.yahoo.com/orkH0C/n97DAA/ySSFAA/IMSolB/TM
---------------------------------------------------------------------~->
To unsubscribe from this group, email
armybuilder-unsubscribe@egroups.com
------------------------------------------------------------------------
There are 4 messages in this issue.
Topics in this digest:
1. Attaching items to child units
From: "Simon Day" <scbd@btopenworld.com>
2. Re: Attaching items to child units
From: "Keith" <mobo@adelphia.net>
3. Re: Attaching items to child units
From: "rjsoz" <rjs@inorbit.com>
4. RE: Attaching items to child units
From: "Day, Simon" <simon.day@capitafhe.co.uk>
________________________________________________________________________
________________________________________________________________________
Message: 1
Date: Sun, 14 Apr 2002 21:55:56 +0100
From: "Simon Day" <scbd@btopenworld.com>
Subject: Attaching items to child units
Hi,
I have come across an interesting problem and was wondering if I am going quietly mad or if there is a way round it.
I have a main unit (Infantry Battalion) which is linked to several child units (HQ, gun company, etc) via an option - this works fine. Because I do not want the child units to be selectable individually, I have added the 'x' to the front of their unique id.
Since I also want the child units to start off with certain items, I have linked these to the specific child units via options and the 'take' syntax.
When running the resulting file within Army builder, the defaulted items are not allocated to the child units, nor am I able to assign the items manually (I get the 'Cannot currently be given any items' message). The parent and each child unit has the number of allowed items set to 9999.
If, however, I return to the creator package and remove the 'x' from the unique id on the child units, then my items are included on the child units when I pick the parent unit (excellent), but the child units are also selectable individually within the system (not so excellent).
Anyone know of a way round this ?
(I'm running version 2.2c)
Cheers,
Simon.
[Non-text portions of this message have been removed]
________________________________________________________________________
________________________________________________________________________
Message: 2
Date: Sun, 14 Apr 2002 22:00:20 -0600
From: "Keith" <mobo@adelphia.net>
Subject: Re: Attaching items to child units
If you add the Ex. attribute "hide" to the child units, that should remove them form the list of units at the top of AB. The user will never be able to select those child units unless another unit gives them the option to select them. Hope this helps.
Thanks,
Keith
----- Original Message -----
From: Simon Day
To: Army Builder List
Sent: Sunday, April 14, 2002 2:55 PM
Subject: [AB] Attaching items to child units
Hi,
I have come across an interesting problem and was wondering if I am going quietly mad or if there is a way round it.
I have a main unit (Infantry Battalion) which is linked to several child units (HQ, gun company, etc) via an option - this works fine. Because I do not want the child units to be selectable individually, I have added the 'x' to the front of their unique id.
Since I also want the child units to start off with certain items, I have linked these to the specific child units via options and the 'take' syntax.
When running the resulting file within Army builder, the defaulted items are not allocated to the child units, nor am I able to assign the items manually (I get the 'Cannot currently be given any items' message). The parent and each child unit has the number of allowed items set to 9999.
If, however, I return to the creator package and remove the 'x' from the unique id on the child units, then my items are included on the child units when I pick the parent unit (excellent), but the child units are also selectable individually within the system (not so excellent).
Anyone know of a way round this ?
(I'm running version 2.2c)
Cheers,
Simon.
[Non-text portions of this message have been removed]
Yahoo! Groups Sponsor
ADVERTISEMENT
To unsubscribe from this group, email
armybuilder-unsubscribe@egroups.com
Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
[Non-text portions of this message have been removed]
________________________________________________________________________
________________________________________________________________________
Message: 3
Date: Mon, 15 Apr 2002 06:44:14 -0000
From: "rjsoz" <rjs@inorbit.com>
Subject: Re: Attaching items to child units
It is docuemnted that units without a valid race prefix (ie.
starting with x) cannot take items. As Keith suggested, use the hide
attribute.
Cheers,
Russell.
--- In armybuilder@y..., "Keith" <mobo@a...> wrote:
> If you add the Ex. attribute "hide" to the child units, that
should remove them form the list of units at the top of AB. The
user will never be able to select those child units unless another
unit gives them the option to select them. Hope this helps.
>
> ----- Original Message -----
> From: Simon Day
> To: Army Builder List
> Sent: Sunday, April 14, 2002 2:55 PM
> Subject: [AB] Attaching items to child units
>
>
> Hi,
>
> I have come across an interesting problem and was wondering if I
am going quietly mad or if there is a way round it.
>
> I have a main unit (Infantry Battalion) which is linked to
several child units (HQ, gun company, etc) via an option - this
works fine. Because I do not want the child units to be selectable
individually, I have added the 'x' to the front of their unique id.
>
> Since I also want the child units to start off with certain
items, I have linked these to the specific child units via options
and the 'take' syntax.
>
________________________________________________________________________
________________________________________________________________________
Message: 4
Date: Mon, 15 Apr 2002 07:53:43 +0100
From: "Day, Simon" <simon.day@capitafhe.co.uk>
Subject: RE: Attaching items to child units
Thanks guys - I'll give that a try.
Cheers,
Simon Day
> -----Original Message-----
> From: rjsoz [SMTP:rjs@inorbit.com]
> Sent: 15 April 2002 07:44
> To: armybuilder@yahoogroups.com
> Subject: Re: [AB] Attaching items to child units
>
> It is docuemnted that units without a valid race prefix (ie.
> starting with x) cannot take items. As Keith suggested, use the hide
> attribute.
>
> Cheers,
> Russell.
>
> --- In armybuilder@y..., "Keith" <mobo@a...> wrote:
> > If you add the Ex. attribute "hide" to the child units, that
> should remove them form the list of units at the top of AB. The
> user will never be able to select those child units unless another
> unit gives them the option to select them. Hope this helps.
> >
> > ----- Original Message -----
> > From: Simon Day
> > To: Army Builder List
> > Sent: Sunday, April 14, 2002 2:55 PM
> > Subject: [AB] Attaching items to child units
> >
> >
> > Hi,
> >
> > I have come across an interesting problem and was wondering if I
> am going quietly mad or if there is a way round it.
> >
> > I have a main unit (Infantry Battalion) which is linked to
> several child units (HQ, gun company, etc) via an option - this
> works fine. Because I do not want the child units to be selectable
> individually, I have added the 'x' to the front of their unique id.
> >
> > Since I also want the child units to start off with certain
> items, I have linked these to the specific child units via options
> and the 'take' syntax.
> >
>
>
>
>
> To unsubscribe from this group, email
>
> armybuilder-unsubscribe@egroups.com
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
>
> ________________________________________________________________________
> This email has been scanned for all viruses by the MessageLabs SkyScan
> service. For more information on a proactive anti-virus service working
> around the clock, around the globe, visit http://www.messagelabs.com
> ________________________________________________________________________
________________________________________________________________________
This email has been scanned for all viruses by the MessageLabs SkyScan
service. For more information on a proactive anti-virus service working
around the clock, around the globe, visit http://www.messagelabs.com
________________________________________________________________________
________________________________________________________________________
________________________________________________________________________
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/