Opened 11 years ago

Closed 11 years ago

#1775 closed enhancement (wontfix)

Indicate previous status of an idle worker

Reported by: eingousef Owned by:
Priority: Nice to Have Milestone:
Component: Core engine Keywords:
Cc: Patch:

Description

I think this happens to all of us : seeing workers waiting next to a dropsite after they've finished their task, and not remembering which resource they were gathering before. An indication of the previous task under the name of the unit when you click on it, for example (woodcutter, hunter, shepherd...) could solve this.

Change History (9)

comment:1 by Erik Johansson, 11 years ago

I guess it could be done by simply (simply as in, without adding more clutter to the GUI, I don't know how easy/difficult it would be to implement) having the icon remain where the gathered resources are listed, even after it has dropped them off.

comment:2 by zoot, 11 years ago

Hmm. What happens to me is seeing workers waiting next to a dropsite and being annoyed that I didn't put them to work again earlier. What they did before is not really important, IMO. You should assign tasks to your workers based on what you currently need, not what you made them do in the past.

#643 might be more in line with what you need.

in reply to:  2 comment:3 by eingousef, 11 years ago

Replying to zoot:

You should assign tasks to your workers based on what you currently need, not what you made them do in the past.

I was going to answer that I need to know which resource I will need in order to dispatch my worker cleverly, but your #643 proposal solves the problem. :)

comment:4 by zoot, 11 years ago

Resolution: duplicate
Status: newclosed

Assuming this is resolved as duplicate of #643. Reverse if not.

comment:5 by leper, 11 years ago

Milestone: Backlog

comment:6 by Kieran P, 11 years ago

Milestone: Backlog
Resolution: duplicate
Status: closedreopened

No, #643 is different functionality. This ticket still needs to be done.

comment:7 by zoot, 11 years ago

It's different functionality but the reporter says it solves his problem.

in reply to:  6 comment:8 by eingousef, 11 years ago

Replying to k776:

No, #643 is different functionality. This ticket still needs to be done.

What problem deriving from this bug do you think about, which would not be solved by the resolution of #643 ?

comment:9 by Kieran P, 11 years ago

Milestone: Backlog
Resolution: wontfix
Status: reopenedclosed

I see. I didn't read the comments, I only read the descriptions, which described completely different functionality. But if #643 will make this ticket redundant, I'll mark it as 'wontfix'.

Note: See TracTickets for help on using tickets.