Hi Gorodoff,

I tried to set up an example of what you described and I could not reproduce 
your problem. 

It is dificult without seeing your module. 

I had a Global key trigger a 'Move fixed distance', then 'Place Marker' and the 
Place Marker was created at the new location.

No doubt I have not recreated your situation exactly. I'm happy to have a look 
at the problem in your module specifically if you can email it to me or point 
me to a location to download it.

Regards,
Brent.
*********** REPLY SEPARATOR ***********

On 3/12/2005 at 2:01 PM Gorodoff wrote:
Hello Brent,

I am under vassal 2.4.2 and jre 1.5 but the problem of "old location 
versus new location" is still there

Does Rodney plan to change this for next release?
In the meantime, is there a way to turn this around?

Cheers,
Gorodoff

--- In [email protected], "Brent Easton" <[EMAIL PROTECTED]> 
wrote:
>
> Hi Gorodoff,
> 
> Comments below,
> 
> Cheers,
> Brent.
> 
> *********** REPLY SEPARATOR ***********
> 
> On 2/12/2005 at 5:50 PM Gorodoff wrote:
> >Hello all,
> >
> >Playing around with GlobalKeyCommand and TriggerKey, I discovered 
2 
> >things:
> >
> >1)On a piece, if a globalkey is not assigned a menu text, to hide 
it 
> >from the rigthclick menu, I get "An untrapped error has occured. 
> >ArrayIndexOutOfBoundsException 0".
> 
> 
> Thanks, this is a bug. I have passed a fix onto Rodney.
> 
> 
> >2)On a piece, I have a movefixeddist trait trigged by alt c, 
followed 
> >by 2 GKC traits that modify graphics on the board (needed because 
2 
> >different range needed), both triggered by alt b
> >The repeated sequence of keys (alt c, alt b) works just fine.
> >
> >So I decide to use a triggerkey with no menu nor shortcut, just to 
> >watch for alt c and trigger alt b automatically
> >
> >It doesn't work fine because alt b seems to be triggered from the 
> >starting position, not the moved to position (old location versus 
new 
> >location)
> >
> >It is the same if I change traits place in the piece definition
> >same with a trigger triggering both alt c and alt b technics
> >same if I change the order of shortcuts on the 'to be trigger' 
> >definition
> >same if I use a trigger to fire alt c, followed by a 'nested' 2nd 
> >trigger watching alt c and firing alt b
> >
> >Is there a way to turn this around?
> 
> 
> Rodney had actually just changed this. Can you try the latest 
version of VASSAL (2.4.2) and see if this fixes this problem for you?
> 
> 
> 
> >Regards,
> >Gorodoff
> 
> ____________________________________________________________
> Brent Easton                       
> Analyst/Programmer                               
> University of Western Sydney                                   
> Email: [EMAIL PROTECTED]
>







SPONSORED LINKS Card games Game pieces Wargaming 
Game play Vassal Personal use 



YAHOO! GROUPS LINKS 

 Visit your group "vassalengine" on the web.
  
 To unsubscribe from this group, send an email to:
 [EMAIL PROTECTED]
  
 Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. 
____________________________________________________________
Brent Easton                       
Analyst/Programmer                               
University of Western Sydney                                   
Email: [EMAIL PROTECTED]



[Non-text portions of this message have been removed]



------------------------ Yahoo! Groups Sponsor --------------------~--> 
Get fast access to your favorite Yahoo! Groups. Make Yahoo! your home page
http://us.click.yahoo.com/dpRU5A/wUILAA/yQLSAA/IMSolB/TM
--------------------------------------------------------------------~-> 

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/vassalengine/

<*> To unsubscribe from this group, send an email to:
    [EMAIL PROTECTED]

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



Reply via email to