A
armybuilder at yahoogroup
Guest
------------------------ Yahoo! Groups Sponsor ---------------------~-->
Free $5 Love Reading
Risk Free!
http://us.click.yahoo.com/3PCXaC/PfREAA/Ey.GAA/IMSolB/TM
---------------------------------------------------------------------~->
To unsubscribe from this group, email
armybuilder-unsubscribe@egroups.com
------------------------------------------------------------------------
There are 11 messages in this issue.
Topics in this digest:
1. Re: Digest Number 716
From: "Christepher McKenney" <blazetopast@hotmail.com>
2. Making rang: work with variable unit sizes
From: "Keith" <mobo@adelphia.net>
3. Re: Making rang: work with variable unit sizes
From: "rjsoz" <rjs@inorbit.com>
4. Re: Re: Making rang: work with variable unit sizes
From: "Keith" <mobo@adelphia.net>
5. Pop up info
From: "Keith" <mobo@adelphia.net>
6. Re: Pop up info
From: "rjsoz" <rjs@inorbit.com>
7. Re: Making rang: work with variable unit sizes
From: "rjsoz" <rjs@inorbit.com>
8. Re: Re: Pop up info
From: "Keith" <mobo@adelphia.net>
9. Re: Re: Making rang: work with variable unit sizes
From: "Keith" <mobo@adelphia.net>
10. Re: Pop up info
From: "rjsoz" <rjs@inorbit.com>
11. Re: Re: Pop up info
From: "Keith" <mobo@adelphia.net>
________________________________________________________________________
________________________________________________________________________
Message: 1
Date: Tue, 25 Jun 2002 07:47:52 -0400
From: "Christepher McKenney" <blazetopast@hotmail.com>
Subject: Re: Digest Number 716
----Original Message Follows----
From: armybuilder@yahoogroups.com
From: "Okami_MyrrhIbis" <myrrhibis@yahoo.com>
Subject: Adding WH Skirmish to AB?
Apologies if this has been addressed elsewhere in the threads, but
will there be a Skirmish ruleset for AB? Right now, you will always
get validation error messages when making up Skirmish warbands.
--------------------------------
A whole new set of files will be needed for Skirmish. It is not a simple
change from the regular Armybuilder files. I am currently not working on it
either.
Christepher McKenney
WFBv6 Armybuilder Files Manager
_________________________________________________________________
MSN Photos is the easiest way to share and print your photos:
http://photos.msn.com/support/worldwide.aspx
________________________________________________________________________
________________________________________________________________________
Message: 2
Date: Tue, 25 Jun 2002 10:14:17 -0600
From: "Keith" <mobo@adelphia.net>
Subject: Making rang: work with variable unit sizes
Just noticed that my rang: weapons can always be increased to the max range set, even if the unit is not that large. I gave the units rmdr: Should that not control how many of the rang: options they can have?
Thanks,
Keith
[Non-text portions of this message have been removed]
________________________________________________________________________
________________________________________________________________________
Message: 3
Date: Wed, 26 Jun 2002 01:41:50 -0000
From: "rjsoz" <rjs@inorbit.com>
Subject: Re: Making rang: work with variable unit sizes
--- In armybuilder@y..., "Keith" <mobo@a...> wrote:
> Just noticed that my rang: weapons can always be increased to the
max range set, even if the unit is not that large. I gave the units
rmdr: Should that not control how many of the rang: options they
can have?
>
rmdr: only controls the range of the actual option that is having
the rmdr assigned to... and only if you specify # as the remainder
count...
In the past, this sort of problem has been flagged with a validation
error - something like: "You have more X than you have members in
that unit!"...
You could do something really messy to force the rule...
Use a high priority option to set a stat to the model count (as I
suggested before, stat:MC=(#) (after defining MC to be a hidden stat
in your def file), then have a number of options for
your "selectable count" weapons that equal the number of possible
models in the unit. Each of these options has attributes:
rang:0-x (where x is the model count)
usta:MC=x (where x is the same number as above)
That way the maximum value of the rang: option increases as you
increase the model count for the unit...
Example: If I had a unit size of 5-10 models, I would have 6 almost
identical options (same name, different id) all linked to the unit.
They would have the following attributes:
rang:0-5,usta:MC=5
rang:0-6,usta:MC=6
rang:0-7,usta:MC=7
rang:0-8,usta:MC=8
rang:0-9,usta:MC=9
rang:0-10,usta:MC=10
That way, your rmdr attribute should apply the remainder (up to the
model count presumably) as appropriate...
DISCLAIMER: I haven't tried any of this!
Cheers,
Russell
--
Russell Sparkes, rjs@inorbit.com, http://www24.brinkster.com/rjsoz
"Experience is what you get just after you needed it" - Unknown
________________________________________________________________________
________________________________________________________________________
Message: 4
Date: Tue, 25 Jun 2002 20:49:21 -0600
From: "Keith" <mobo@adelphia.net>
Subject: Re: Re: Making rang: work with variable unit sizes
Thanks Russell. I may give that a shot. I thought that AB used to tell you
if you had more weapons then guys to carry them. Can it still do that and
how?
Thanks,
Keith
----- Original Message -----
From: "rjsoz" <rjs@inorbit.com>
To: ab@support.wolflair.com
Sent: Tuesday, June 25, 2002 7:41 PM
Subject: [AB] Re: Making rang: work with variable unit sizes
> --- In armybuilder@y..., "Keith" <mobo@a...> wrote:
> > Just noticed that my rang: weapons can always be increased to the
> max range set, even if the unit is not that large. I gave the units
> rmdr: Should that not control how many of the rang: options they
> can have?
> >
> rmdr: only controls the range of the actual option that is having
> the rmdr assigned to... and only if you specify # as the remainder
> count...
>
> In the past, this sort of problem has been flagged with a validation
> error - something like: "You have more X than you have members in
> that unit!"...
>
> You could do something really messy to force the rule...
> Use a high priority option to set a stat to the model count (as I
> suggested before, stat:MC=(#) (after defining MC to be a hidden stat
> in your def file), then have a number of options for
> your "selectable count" weapons that equal the number of possible
> models in the unit. Each of these options has attributes:
> rang:0-x (where x is the model count)
> usta:MC=x (where x is the same number as above)
> That way the maximum value of the rang: option increases as you
> increase the model count for the unit...
>
> Example: If I had a unit size of 5-10 models, I would have 6 almost
> identical options (same name, different id) all linked to the unit.
> They would have the following attributes:
> rang:0-5,usta:MC=5
> rang:0-6,usta:MC=6
> rang:0-7,usta:MC=7
> rang:0-8,usta:MC=8
> rang:0-9,usta:MC=9
> rang:0-10,usta:MC=10
>
>
> That way, your rmdr attribute should apply the remainder (up to the
> model count presumably) as appropriate...
>
> DISCLAIMER: I haven't tried any of this!
>
> Cheers,
> Russell
> --
> Russell Sparkes, rjs@inorbit.com, http://www24.brinkster.com/rjsoz
> "Experience is what you get just after you needed it" - Unknown
>
>
>
> To unsubscribe from this group, email
>
> armybuilder-unsubscribe@egroups.com
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
________________________________________________________________________
________________________________________________________________________
Message: 5
Date: Tue, 25 Jun 2002 21:11:00 -0600
From: "Keith" <mobo@adelphia.net>
Subject: Pop up info
Is there a way to make AB flag an invalid option when there really is not one? Also, it might be a useful tool to add pop up messages to users in a future version of AB. That way they would have to look at the notes that you deem very important to read. Maybe make them click OK to clear the pop up. Just and ideal Rob.
Thanks,
Keith
[Non-text portions of this message have been removed]
________________________________________________________________________
________________________________________________________________________
Message: 6
Date: Wed, 26 Jun 2002 03:36:43 -0000
From: "rjsoz" <rjs@inorbit.com>
Subject: Re: Pop up info
--- In armybuilder@y..., "Keith" <mobo@a...> wrote:
> Is there a way to make AB flag an invalid option when there really
is not one? Also, it might be a useful tool to add pop up messages
to users in a future version of AB. That way they would have to
look at the notes that you deem very important to read. Maybe make
them click OK to clear the pop up. Just and ideal Rob.
>
You can flag a pop-up when new rosters are created, or you can
specify messages on every printout for a certain race...
Check the info: race attribute
If you use an Augment rule to augment the xx race, you can apply one
info: attribute to all races...
If you have special information that you think should be popped up
before the user chooses a race, you can use the lnch: race attribute.
Is that why you want to flag a validation message? These two
mechanisms may be what you're really after.
Cheers,
Russell
--
Russell Sparkes, rjs@inorbit.com, http://www24.brinkster.com/rjsoz
"Experience is what you get just after you needed it" - Unknown
________________________________________________________________________
________________________________________________________________________
Message: 7
Date: Wed, 26 Jun 2002 03:42:17 -0000
From: "rjsoz" <rjs@inorbit.com>
Subject: Re: Making rang: work with variable unit sizes
--- In armybuilder@y..., "Keith" <mobo@a...> wrote:
> Thanks Russell. I may give that a shot. I thought that AB used
> to tell you if you had more weapons then guys to carry them. Can
> it still do that and how?
>
You'll need to specify a validation message. You can check out the
ocat: external unit attribute. The help text is quite long, and
there's some stuff near the bottom about using it with rang: options.
Cheers,
Russell.
--
Russell Sparkes, rjs@inorbit.com, http://www24.brinkster.com/rjsoz
"Experience is what you get just after you needed it" - Unknown
________________________________________________________________________
________________________________________________________________________
Message: 8
Date: Tue, 25 Jun 2002 21:42:49 -0600
From: "Keith" <mobo@adelphia.net>
Subject: Re: Re: Pop up info
I'd like to have a pop up when a unit or option is selected my the user.
Thanks,
Keith
----- Original Message -----
From: "rjsoz" <rjs@inorbit.com>
To: ab@support.wolflair.com
Sent: Tuesday, June 25, 2002 9:36 PM
Subject: [AB] Re: Pop up info
> --- In armybuilder@y..., "Keith" <mobo@a...> wrote:
> > Is there a way to make AB flag an invalid option when there really
> is not one? Also, it might be a useful tool to add pop up messages
> to users in a future version of AB. That way they would have to
> look at the notes that you deem very important to read. Maybe make
> them click OK to clear the pop up. Just and ideal Rob.
> >
>
> You can flag a pop-up when new rosters are created, or you can
> specify messages on every printout for a certain race...
> Check the info: race attribute
>
> If you use an Augment rule to augment the xx race, you can apply one
> info: attribute to all races...
> If you have special information that you think should be popped up
> before the user chooses a race, you can use the lnch: race attribute.
>
> Is that why you want to flag a validation message? These two
> mechanisms may be what you're really after.
>
> Cheers,
> Russell
> --
> Russell Sparkes, rjs@inorbit.com, http://www24.brinkster.com/rjsoz
> "Experience is what you get just after you needed it" - Unknown
>
>
>
> To unsubscribe from this group, email
>
> armybuilder-unsubscribe@egroups.com
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
________________________________________________________________________
________________________________________________________________________
Message: 9
Date: Tue, 25 Jun 2002 21:43:18 -0600
From: "Keith" <mobo@adelphia.net>
Subject: Re: Re: Making rang: work with variable unit sizes
Will do thanks.
Thanks,
Keith
----- Original Message -----
From: "rjsoz" <rjs@inorbit.com>
To: ab@support.wolflair.com
Sent: Tuesday, June 25, 2002 9:42 PM
Subject: [AB] Re: Making rang: work with variable unit sizes
> --- In armybuilder@y..., "Keith" <mobo@a...> wrote:
> > Thanks Russell. I may give that a shot. I thought that AB used
> > to tell you if you had more weapons then guys to carry them. Can
> > it still do that and how?
> >
> You'll need to specify a validation message. You can check out the
> ocat: external unit attribute. The help text is quite long, and
> there's some stuff near the bottom about using it with rang: options.
>
> Cheers,
> Russell.
> --
> Russell Sparkes, rjs@inorbit.com, http://www24.brinkster.com/rjsoz
> "Experience is what you get just after you needed it" - Unknown
>
>
>
> To unsubscribe from this group, email
>
> armybuilder-unsubscribe@egroups.com
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
________________________________________________________________________
________________________________________________________________________
Message: 10
Date: Wed, 26 Jun 2002 04:13:59 -0000
From: "rjsoz" <rjs@inorbit.com>
Subject: Re: Pop up info
--- In armybuilder@y..., "Keith" <mobo@a...> wrote:
> I'd like to have a pop up when a unit or option is selected my the
> user.
Hmm, fair enough - you wont get that with the current version of AB.
You could insert an option that immediately flags a validation error
as soon as the unit is added to the roster. The user then has to
unselect (or select depending on how you want it setup) the option
to indicate they have read the "pop-up".
You could do this with a type: option attribute and a tloc: unit
attribute like this...
Option:
id=oFlagErr name="Warning Message" attributes=type:FlagError
Unit:
link to oFlagErr=free
internal attributes=dflt
FlagErr
external attributes=tloc:is=FlagError-msg=feMsgId
Messgae:
id=feMsgId text="You should really know xyz about the unit you have
just selected, unselect the Warning Message option for ^u to clear
this message"
Or you could switch it around so the option is not selected by
default (remove the dflt: attribute) and change the tloc to be "not"
instead of "is".
Just an option
Cheers,
Russell
--
Russell Sparkes, rjs@inorbit.com, http://www24.brinkster.com/rjsoz
"Experience is what you get just after you needed it" - Unknown
________________________________________________________________________
________________________________________________________________________
Message: 11
Date: Wed, 26 Jun 2002 07:03:43 -0600
From: "Keith" <mobo@adelphia.net>
Subject: Re: Re: Pop up info
Thanks for all the help. You've given me a few things to try out.
Thanks,
Keith
----- Original Message -----
From: "rjsoz" <rjs@inorbit.com>
To: ab@support.wolflair.com
Sent: Tuesday, June 25, 2002 10:13 PM
Subject: [AB] Re: Pop up info
> --- In armybuilder@y..., "Keith" <mobo@a...> wrote:
> > I'd like to have a pop up when a unit or option is selected my the
> > user.
>
> Hmm, fair enough - you wont get that with the current version of AB.
> You could insert an option that immediately flags a validation error
> as soon as the unit is added to the roster. The user then has to
> unselect (or select depending on how you want it setup) the option
> to indicate they have read the "pop-up".
>
> You could do this with a type: option attribute and a tloc: unit
> attribute like this...
> Option:
> id=oFlagErr name="Warning Message" attributes=type:FlagError
>
> Unit:
> link to oFlagErr=free
> internal attributes=dfltFlagErr
> external attributes=tloc:is=FlagError-msg=feMsgId
>
> Messgae:
> id=feMsgId text="You should really know xyz about the unit you have
> just selected, unselect the Warning Message option for ^u to clear
> this message"
>
> Or you could switch it around so the option is not selected by
> default (remove the dflt: attribute) and change the tloc to be "not"
> instead of "is".
> Just an option
>
> Cheers,
> Russell
> --
> Russell Sparkes, rjs@inorbit.com, http://www24.brinkster.com/rjsoz
> "Experience is what you get just after you needed it" - Unknown
>
>
>
> To unsubscribe from this group, email
>
> armybuilder-unsubscribe@egroups.com
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
________________________________________________________________________
________________________________________________________________________
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
Free $5 Love Reading
Risk Free!
http://us.click.yahoo.com/3PCXaC/PfREAA/Ey.GAA/IMSolB/TM
---------------------------------------------------------------------~->
To unsubscribe from this group, email
armybuilder-unsubscribe@egroups.com
------------------------------------------------------------------------
There are 11 messages in this issue.
Topics in this digest:
1. Re: Digest Number 716
From: "Christepher McKenney" <blazetopast@hotmail.com>
2. Making rang: work with variable unit sizes
From: "Keith" <mobo@adelphia.net>
3. Re: Making rang: work with variable unit sizes
From: "rjsoz" <rjs@inorbit.com>
4. Re: Re: Making rang: work with variable unit sizes
From: "Keith" <mobo@adelphia.net>
5. Pop up info
From: "Keith" <mobo@adelphia.net>
6. Re: Pop up info
From: "rjsoz" <rjs@inorbit.com>
7. Re: Making rang: work with variable unit sizes
From: "rjsoz" <rjs@inorbit.com>
8. Re: Re: Pop up info
From: "Keith" <mobo@adelphia.net>
9. Re: Re: Making rang: work with variable unit sizes
From: "Keith" <mobo@adelphia.net>
10. Re: Pop up info
From: "rjsoz" <rjs@inorbit.com>
11. Re: Re: Pop up info
From: "Keith" <mobo@adelphia.net>
________________________________________________________________________
________________________________________________________________________
Message: 1
Date: Tue, 25 Jun 2002 07:47:52 -0400
From: "Christepher McKenney" <blazetopast@hotmail.com>
Subject: Re: Digest Number 716
----Original Message Follows----
From: armybuilder@yahoogroups.com
From: "Okami_MyrrhIbis" <myrrhibis@yahoo.com>
Subject: Adding WH Skirmish to AB?
Apologies if this has been addressed elsewhere in the threads, but
will there be a Skirmish ruleset for AB? Right now, you will always
get validation error messages when making up Skirmish warbands.
--------------------------------
A whole new set of files will be needed for Skirmish. It is not a simple
change from the regular Armybuilder files. I am currently not working on it
either.
Christepher McKenney
WFBv6 Armybuilder Files Manager
_________________________________________________________________
MSN Photos is the easiest way to share and print your photos:
http://photos.msn.com/support/worldwide.aspx
________________________________________________________________________
________________________________________________________________________
Message: 2
Date: Tue, 25 Jun 2002 10:14:17 -0600
From: "Keith" <mobo@adelphia.net>
Subject: Making rang: work with variable unit sizes
Just noticed that my rang: weapons can always be increased to the max range set, even if the unit is not that large. I gave the units rmdr: Should that not control how many of the rang: options they can have?
Thanks,
Keith
[Non-text portions of this message have been removed]
________________________________________________________________________
________________________________________________________________________
Message: 3
Date: Wed, 26 Jun 2002 01:41:50 -0000
From: "rjsoz" <rjs@inorbit.com>
Subject: Re: Making rang: work with variable unit sizes
--- In armybuilder@y..., "Keith" <mobo@a...> wrote:
> Just noticed that my rang: weapons can always be increased to the
max range set, even if the unit is not that large. I gave the units
rmdr: Should that not control how many of the rang: options they
can have?
>
rmdr: only controls the range of the actual option that is having
the rmdr assigned to... and only if you specify # as the remainder
count...
In the past, this sort of problem has been flagged with a validation
error - something like: "You have more X than you have members in
that unit!"...
You could do something really messy to force the rule...
Use a high priority option to set a stat to the model count (as I
suggested before, stat:MC=(#) (after defining MC to be a hidden stat
in your def file), then have a number of options for
your "selectable count" weapons that equal the number of possible
models in the unit. Each of these options has attributes:
rang:0-x (where x is the model count)
usta:MC=x (where x is the same number as above)
That way the maximum value of the rang: option increases as you
increase the model count for the unit...
Example: If I had a unit size of 5-10 models, I would have 6 almost
identical options (same name, different id) all linked to the unit.
They would have the following attributes:
rang:0-5,usta:MC=5
rang:0-6,usta:MC=6
rang:0-7,usta:MC=7
rang:0-8,usta:MC=8
rang:0-9,usta:MC=9
rang:0-10,usta:MC=10
That way, your rmdr attribute should apply the remainder (up to the
model count presumably) as appropriate...
DISCLAIMER: I haven't tried any of this!
Cheers,
Russell
--
Russell Sparkes, rjs@inorbit.com, http://www24.brinkster.com/rjsoz
"Experience is what you get just after you needed it" - Unknown
________________________________________________________________________
________________________________________________________________________
Message: 4
Date: Tue, 25 Jun 2002 20:49:21 -0600
From: "Keith" <mobo@adelphia.net>
Subject: Re: Re: Making rang: work with variable unit sizes
Thanks Russell. I may give that a shot. I thought that AB used to tell you
if you had more weapons then guys to carry them. Can it still do that and
how?
Thanks,
Keith
----- Original Message -----
From: "rjsoz" <rjs@inorbit.com>
To: ab@support.wolflair.com
Sent: Tuesday, June 25, 2002 7:41 PM
Subject: [AB] Re: Making rang: work with variable unit sizes
> --- In armybuilder@y..., "Keith" <mobo@a...> wrote:
> > Just noticed that my rang: weapons can always be increased to the
> max range set, even if the unit is not that large. I gave the units
> rmdr: Should that not control how many of the rang: options they
> can have?
> >
> rmdr: only controls the range of the actual option that is having
> the rmdr assigned to... and only if you specify # as the remainder
> count...
>
> In the past, this sort of problem has been flagged with a validation
> error - something like: "You have more X than you have members in
> that unit!"...
>
> You could do something really messy to force the rule...
> Use a high priority option to set a stat to the model count (as I
> suggested before, stat:MC=(#) (after defining MC to be a hidden stat
> in your def file), then have a number of options for
> your "selectable count" weapons that equal the number of possible
> models in the unit. Each of these options has attributes:
> rang:0-x (where x is the model count)
> usta:MC=x (where x is the same number as above)
> That way the maximum value of the rang: option increases as you
> increase the model count for the unit...
>
> Example: If I had a unit size of 5-10 models, I would have 6 almost
> identical options (same name, different id) all linked to the unit.
> They would have the following attributes:
> rang:0-5,usta:MC=5
> rang:0-6,usta:MC=6
> rang:0-7,usta:MC=7
> rang:0-8,usta:MC=8
> rang:0-9,usta:MC=9
> rang:0-10,usta:MC=10
>
>
> That way, your rmdr attribute should apply the remainder (up to the
> model count presumably) as appropriate...
>
> DISCLAIMER: I haven't tried any of this!
>
> Cheers,
> Russell
> --
> Russell Sparkes, rjs@inorbit.com, http://www24.brinkster.com/rjsoz
> "Experience is what you get just after you needed it" - Unknown
>
>
>
> To unsubscribe from this group, email
>
> armybuilder-unsubscribe@egroups.com
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
________________________________________________________________________
________________________________________________________________________
Message: 5
Date: Tue, 25 Jun 2002 21:11:00 -0600
From: "Keith" <mobo@adelphia.net>
Subject: Pop up info
Is there a way to make AB flag an invalid option when there really is not one? Also, it might be a useful tool to add pop up messages to users in a future version of AB. That way they would have to look at the notes that you deem very important to read. Maybe make them click OK to clear the pop up. Just and ideal Rob.
Thanks,
Keith
[Non-text portions of this message have been removed]
________________________________________________________________________
________________________________________________________________________
Message: 6
Date: Wed, 26 Jun 2002 03:36:43 -0000
From: "rjsoz" <rjs@inorbit.com>
Subject: Re: Pop up info
--- In armybuilder@y..., "Keith" <mobo@a...> wrote:
> Is there a way to make AB flag an invalid option when there really
is not one? Also, it might be a useful tool to add pop up messages
to users in a future version of AB. That way they would have to
look at the notes that you deem very important to read. Maybe make
them click OK to clear the pop up. Just and ideal Rob.
>
You can flag a pop-up when new rosters are created, or you can
specify messages on every printout for a certain race...
Check the info: race attribute
If you use an Augment rule to augment the xx race, you can apply one
info: attribute to all races...
If you have special information that you think should be popped up
before the user chooses a race, you can use the lnch: race attribute.
Is that why you want to flag a validation message? These two
mechanisms may be what you're really after.
Cheers,
Russell
--
Russell Sparkes, rjs@inorbit.com, http://www24.brinkster.com/rjsoz
"Experience is what you get just after you needed it" - Unknown
________________________________________________________________________
________________________________________________________________________
Message: 7
Date: Wed, 26 Jun 2002 03:42:17 -0000
From: "rjsoz" <rjs@inorbit.com>
Subject: Re: Making rang: work with variable unit sizes
--- In armybuilder@y..., "Keith" <mobo@a...> wrote:
> Thanks Russell. I may give that a shot. I thought that AB used
> to tell you if you had more weapons then guys to carry them. Can
> it still do that and how?
>
You'll need to specify a validation message. You can check out the
ocat: external unit attribute. The help text is quite long, and
there's some stuff near the bottom about using it with rang: options.
Cheers,
Russell.
--
Russell Sparkes, rjs@inorbit.com, http://www24.brinkster.com/rjsoz
"Experience is what you get just after you needed it" - Unknown
________________________________________________________________________
________________________________________________________________________
Message: 8
Date: Tue, 25 Jun 2002 21:42:49 -0600
From: "Keith" <mobo@adelphia.net>
Subject: Re: Re: Pop up info
I'd like to have a pop up when a unit or option is selected my the user.
Thanks,
Keith
----- Original Message -----
From: "rjsoz" <rjs@inorbit.com>
To: ab@support.wolflair.com
Sent: Tuesday, June 25, 2002 9:36 PM
Subject: [AB] Re: Pop up info
> --- In armybuilder@y..., "Keith" <mobo@a...> wrote:
> > Is there a way to make AB flag an invalid option when there really
> is not one? Also, it might be a useful tool to add pop up messages
> to users in a future version of AB. That way they would have to
> look at the notes that you deem very important to read. Maybe make
> them click OK to clear the pop up. Just and ideal Rob.
> >
>
> You can flag a pop-up when new rosters are created, or you can
> specify messages on every printout for a certain race...
> Check the info: race attribute
>
> If you use an Augment rule to augment the xx race, you can apply one
> info: attribute to all races...
> If you have special information that you think should be popped up
> before the user chooses a race, you can use the lnch: race attribute.
>
> Is that why you want to flag a validation message? These two
> mechanisms may be what you're really after.
>
> Cheers,
> Russell
> --
> Russell Sparkes, rjs@inorbit.com, http://www24.brinkster.com/rjsoz
> "Experience is what you get just after you needed it" - Unknown
>
>
>
> To unsubscribe from this group, email
>
> armybuilder-unsubscribe@egroups.com
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
________________________________________________________________________
________________________________________________________________________
Message: 9
Date: Tue, 25 Jun 2002 21:43:18 -0600
From: "Keith" <mobo@adelphia.net>
Subject: Re: Re: Making rang: work with variable unit sizes
Will do thanks.
Thanks,
Keith
----- Original Message -----
From: "rjsoz" <rjs@inorbit.com>
To: ab@support.wolflair.com
Sent: Tuesday, June 25, 2002 9:42 PM
Subject: [AB] Re: Making rang: work with variable unit sizes
> --- In armybuilder@y..., "Keith" <mobo@a...> wrote:
> > Thanks Russell. I may give that a shot. I thought that AB used
> > to tell you if you had more weapons then guys to carry them. Can
> > it still do that and how?
> >
> You'll need to specify a validation message. You can check out the
> ocat: external unit attribute. The help text is quite long, and
> there's some stuff near the bottom about using it with rang: options.
>
> Cheers,
> Russell.
> --
> Russell Sparkes, rjs@inorbit.com, http://www24.brinkster.com/rjsoz
> "Experience is what you get just after you needed it" - Unknown
>
>
>
> To unsubscribe from this group, email
>
> armybuilder-unsubscribe@egroups.com
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
________________________________________________________________________
________________________________________________________________________
Message: 10
Date: Wed, 26 Jun 2002 04:13:59 -0000
From: "rjsoz" <rjs@inorbit.com>
Subject: Re: Pop up info
--- In armybuilder@y..., "Keith" <mobo@a...> wrote:
> I'd like to have a pop up when a unit or option is selected my the
> user.
Hmm, fair enough - you wont get that with the current version of AB.
You could insert an option that immediately flags a validation error
as soon as the unit is added to the roster. The user then has to
unselect (or select depending on how you want it setup) the option
to indicate they have read the "pop-up".
You could do this with a type: option attribute and a tloc: unit
attribute like this...
Option:
id=oFlagErr name="Warning Message" attributes=type:FlagError
Unit:
link to oFlagErr=free
internal attributes=dflt
FlagErrexternal attributes=tloc:is=FlagError-msg=feMsgId
Messgae:
id=feMsgId text="You should really know xyz about the unit you have
just selected, unselect the Warning Message option for ^u to clear
this message"
Or you could switch it around so the option is not selected by
default (remove the dflt: attribute) and change the tloc to be "not"
instead of "is".
Just an option
Cheers,
Russell
--
Russell Sparkes, rjs@inorbit.com, http://www24.brinkster.com/rjsoz
"Experience is what you get just after you needed it" - Unknown
________________________________________________________________________
________________________________________________________________________
Message: 11
Date: Wed, 26 Jun 2002 07:03:43 -0600
From: "Keith" <mobo@adelphia.net>
Subject: Re: Re: Pop up info
Thanks for all the help. You've given me a few things to try out.
Thanks,
Keith
----- Original Message -----
From: "rjsoz" <rjs@inorbit.com>
To: ab@support.wolflair.com
Sent: Tuesday, June 25, 2002 10:13 PM
Subject: [AB] Re: Pop up info
> --- In armybuilder@y..., "Keith" <mobo@a...> wrote:
> > I'd like to have a pop up when a unit or option is selected my the
> > user.
>
> Hmm, fair enough - you wont get that with the current version of AB.
> You could insert an option that immediately flags a validation error
> as soon as the unit is added to the roster. The user then has to
> unselect (or select depending on how you want it setup) the option
> to indicate they have read the "pop-up".
>
> You could do this with a type: option attribute and a tloc: unit
> attribute like this...
> Option:
> id=oFlagErr name="Warning Message" attributes=type:FlagError
>
> Unit:
> link to oFlagErr=free
> internal attributes=dflt
FlagErr> external attributes=tloc:is=FlagError-msg=feMsgId
>
> Messgae:
> id=feMsgId text="You should really know xyz about the unit you have
> just selected, unselect the Warning Message option for ^u to clear
> this message"
>
> Or you could switch it around so the option is not selected by
> default (remove the dflt: attribute) and change the tloc to be "not"
> instead of "is".
> Just an option
>
> Cheers,
> Russell
> --
> Russell Sparkes, rjs@inorbit.com, http://www24.brinkster.com/rjsoz
> "Experience is what you get just after you needed it" - Unknown
>
>
>
> To unsubscribe from this group, email
>
> armybuilder-unsubscribe@egroups.com
>
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/
>
>
________________________________________________________________________
________________________________________________________________________
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/