Opened 20 months ago
Last modified 11 months ago
#6617 reopened defect
Mouse pointer incorrect when units are selected that can't be garrisoned in own or allied building
Reported by: | Andy Alt | Owned by: | |
---|---|---|---|
Priority: | If Time Permits | Milestone: | Alpha 27 |
Component: | UI – In-game | Keywords: | |
Cc: | Patch: |
Description (last modified by )
If you have units selected that can't be garrisoned in a building, then hold down ctrl
and hover the mouse over an allied building (or your own), the mouse pointer becomes a sword.
Examples: if infantry is selected and the pointer is over an elephant cage
if elephants are selected, and the pointer is over a barracks.
EDIT
The ticket was originally closed as a wontfix
, but after further testing, the red color of the new action-attack-move
cursor does make it look just something is wrong. The old cursor was more gray, and the problem was perhaps never reported for that reason.
Image with women trying to put them on a wall with the old & new cursor.
possible solution
- see the code snippet in comment:8
Attachments (6)
Change History (17)
comment:1 by , 20 months ago
Milestone: | Alpha 26 → Alpha 27 |
---|
comment:2 by , 16 months ago
Milestone: | Alpha 27 |
---|---|
Resolution: | → invalid |
Status: | new → closed |
The sword is (probably) due to the action being attack-move.
comment:3 by , 16 months ago
Resolution: | invalid |
---|---|
Status: | closed → reopened |
This is a bug. Please review again.
by , 16 months ago
Attachment: | 0ad-6617.png added |
---|
Shows attack/move cursor when a unit can't be garrisoned in own or allied building
comment:4 by , 16 months ago
Milestone: | → Alpha 27 |
---|
comment:5 by , 16 months ago
Difference A25 vs latest dev1 for Siege
- cursor color/ design changes [26448]
- behavior of the
ctrl
key press was changed- unknown changeset
A25 Siege
Latest dev1 Siege
Difference A25 vs latest dev1 for Soldier
A25 Soldier
Latest dev1 Soldier
Footnote
1 latest dev = [27433]
---
Decision required
- close the ticket as
wontfix
- change the cursor when pressing
ctrl
for siege units
by , 16 months ago
Attachment: | a25_siege.png added |
---|
by , 16 months ago
Attachment: | latest_dev_siege.png added |
---|
by , 16 months ago
Attachment: | a25_soldier.png added |
---|
by , 16 months ago
Attachment: | latest_dev_soldier.png added |
---|
comment:6 by , 16 months ago
Description: | modified (diff) |
---|---|
Summary: | If only siege selected, hovering over allied building the mouse pointer is a sword → Mouse pointer incorrect when units are selected that can't be garrisoned in own or allied building |
I realized it happens not only with siege but other units as well. I've tried to update the title and description to be more accurate.
And thanks for all your detective work and pics, Langbart. :)
follow-up: 8 comment:7 by , 15 months ago
I vote for option 1, if that wasn't clear yet. Or convince @wowgetoffyourcellphone that a different cursor is needed.
comment:8 by , 15 months ago
Milestone: | Alpha 27 |
---|---|
Resolution: | → wontfix |
Status: | reopened → closed |
Replying to Langbart:
1. close the ticket as
wontfix
2. change the cursor when pressingctrl
for siege units
Replying to Freagarach:
I vote for option 1
Ticket will be closed as wontfix
.
Below are some Options that I considered to meet the ticket's request and my opinion for each.
Option A: Add an additional check
If another check is added the issue described in the ticket resolves. The default
cursor will be displayed, instead of the attack-move
cursor. Ctrl + right-clicking
would be the same as just right-clicking
. The entity simply walks towards the building.
opinion: If you attempt to useAttack Move
during combat, the cursor could change while accidentally hovering over one of your own units.
-
binaries/data/mods/public/gui/session/unit_actions.js
a b var g_UnitActions = 128 128 { 129 129 if (!entState.unitAI) 130 130 return false; 131 if (targetState && playerCheck(entState, targetState, ["Player", "Ally"])) 132 return false; 131 133 return { "possible": true }; 132 134 }, 133 135 "hotkeyActionCheck": function(target, selection)
Option B: Display a different cursor
The ones listed below are included in the base game.
- opinion: None of the cursors currently match the use case, and if you create one, it would be confusing to have two cursors for the same thing.
Option C: Change
Change back to the old cursor or change the existing one.
name | icon | revision |
---|---|---|
action-attack-move.png | [26447] | |
action-attack-move.png | [26448] |
comment:9 by , 13 months ago
Description: | modified (diff) |
---|---|
Milestone: | → Alpha 27 |
Priority: | Should Have → If Time Permits |
Resolution: | wontfix |
Status: | closed → reopened |
Update description with reason for reopening.
by , 13 months ago
Attachment: | o_n_act_cursor.png added |
---|
comment:10 by , 12 months ago
Milestone: | Alpha 27 → Alpha 28 |
---|
Sounds like A27 Material.