Arx Libertatis Bug Tracker
star_faded.png
Please log in to bookmark issues
bug_report_small.png
CLOSED  Bug report #154  -  Action (mouse) on world objects doesn't change mapping
Posted Jan 27, 2012 - updated Jun 30, 2018   Shortlink: http://arx.vg/154
action_vote_minus_faded.png
0
Votes
 action_vote_plus_faded.png
icon_info.png This issue has been closed with status "Not a bug" and resolution "CAN'T REPRODUCE".
Issue details
  • Type of issue
    Bug report
  • Status
     
    		 Not a bug
  • Assigned to
    Not assigned to anyone
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
  • Posted by
    i30817
  • Owned by
    Not owned by anyone
  • Estimated time
    Not estimated
  • Category
    User interface
  • Resolution
    CAN'T REPRODUCE
  • Priority
    Not determined
  • Reproducability
    Not determined
  • Severity
    Normal
  • Targetted for
    icon_milestones.png Not determined
  • OS
    icon_customdatatype.png Not determined
  • Architecture
    icon_customdatatype.png Not determined
  • Fixed in
    icon_customdatatype.png Not determined
Issue description
I noticed this on the cell at the beginning.

I changed the key mapped thus: 
 move forward -> button1
 Use -> button2
 Action(mouse) -> button2 (to see if i could use both on a single 2 button mouse)
 combatmode -> button3
 precast 1 -> mousewheel up
 inventory -> mousewheel down


However, thereafter i couldn't "Action(mouse)" the bars of the cell with mouse2. It only appears to work for mouse1, since inverting the Use&Action with the move forward allowed me to use them with mouse1.
Steps to reproduce this issue
Nothing entered.

#4
icon_reply.pngReply
Comment posted by
Daniel Scharrer
Jun 30, 16:19
This seems to work with both Arx Libertatis 1.1.2 and with the current development code, although the current development code doesn't let you bind the same button to two different actions through the menu.

The issue was updated with the following change(s):
  • This issue's description has been changed
  • The status has been updated, from New to Not a bug.
  • This issue has been closed
  • The resolution has been updated, from Not determined to CAN'T REPRODUCE.