Closed GoogleCodeExporter closed 9 years ago
This is a test solution to allow to select any mission while keeping mission
briefing window from overlaping other missions. Maybe you can suggest better
solution to the problem? *keeping in mind that we plan to allow custom missions
later on
Original comment by kromster80@gmail.com
on 24 Aug 2010 at 1:44
Maybe I have a solution for this (don't know wether it works): You could spilt
the mission map into 4 squares (just in code, on the screen you can see the
whole map). If you are in the left-down map quarter, the description would be
in the right-down quarter, and so on (if in the left-up quarter -> right-up
quarter, down-right -> down-left). Just an idea.
Original comment by teddy.lo...@gmail.com
on 24 Aug 2010 at 2:07
I don't mean the mouse, but the progress in the missions.
Original comment by teddy.lo...@gmail.com
on 24 Aug 2010 at 2:09
[deleted comment]
I don't understand your idea, since it always the same as in KaM Remake (except
that we've fixed a bug when mission description will jump off screen).
Original comment by kromster80@gmail.com
on 26 Aug 2010 at 4:03
[deleted comment]
You could seperate the mission map into 4 squares. If you are progressed with
the missions into the square, where the description is, it jumps to another
square, and stay there fixed. The idea replaces the system, that the mission
description jumps away from the mause-pointer. I can't describe it better, I'm
german xD.. sry
Original comment by teddy.lo...@gmail.com
on 26 Aug 2010 at 4:10
I see your idea now, thanks, but in KAM Remake you can select to replay any of
previous missions - what if mission player wants to choose is blocked with
description block?
Original comment by kromster80@gmail.com
on 26 Aug 2010 at 4:42
Mh, good point. No sollution in mind. Another idea: make the description part
transparent and place it in the down right part of the map.
Original comment by teddy.lo...@gmail.com
on 26 Aug 2010 at 6:13
I've restricted its movement and now it looks quite better. I think issue is
solved.
Original comment by kromster80@gmail.com
on 2 Oct 2010 at 10:10
Original issue reported on code.google.com by
teddy.lo...@gmail.com
on 24 Aug 2010 at 1:26