[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [glob2-devel] more feedback (many topics)
From: |
Kai Antweiler |
Subject: |
Re: [glob2-devel] more feedback (many topics) |
Date: |
Sun, 15 Apr 2007 09:32:49 +0200 |
User-agent: |
Gnus/5.1007 (Gnus v5.10.7) XEmacs/21.4.20 (linux) |
Bug: when the only offered jobs come from an Inn with full food and no
guests, sometimes a glob harvests wheat. There is no white box.
Only a black box.
> It would be nice if the lines drawn by the "draw unit paths" feature
> (which draws lines that indicate where globules are going and is
> invoked by default by "t") appeared even when neither source nor
> destination are on the screen. This is needed to allow tracking a
> long line across several screens to try to understand where a globule
> is going (and why it is going there!).
It would be nice if buildings get identification tag.
When you click on a glob you could see the tag of the building
it is working for. Or an option that the tags are printed on the
screen. And more convenient: colors. Select a building and all
globs that work for it and the building get some color. Also the
lines from "draw unit paths" get that color.
> the bug tracker on Savannah:
>
> Duplicates do not seem to be linked (at least not automatically). It
> should only be possible to mark a bug report as a duplicate if one
> specifies _which_ other bug report it is a duplicate of. And in that
> case, there should be a link between the two bug reports. This
> doesn't seem to happen (at least not automatically). This means that
> the effort put into a bug report marked as a duplicate is effectively
> lost, because one can not find it from the main bug report. Is there
> some way to fix this?
You can manually add a comment: "marked this as duplicate of ..."
You can suggest this wish to savannah.
We can change the tracker.
I think glob2 could profit from switching to lauchpad.net, but
I don't know if their tracker handles duplicates better.
> Whether a bg report is open or closed is orthogonal to its status.
> This is confusing. Is there some way to tie bug status to whether a
> bug is open or closed?
I like it that way. You can close a bug that is old and has never
been confirmed or fixed without loosing its state. Also you can
mark something as fixed and leave it open for a week or so and
ask others (like the creater of the bug) to check if this really
is really working for him.
> Dragging with the middle mouse button in the main map area to move the
> viewport is not documented. This is a nice feature, but I only found
> out about it by reading bug reports!
> The log files in ~/.glob2/logs continue to grow even when glob2 is
> paused. I left glob2 running overnight paused and it filled my hard
> disk. Ugh.
Do you know which logfiles?
There are many of them.
We should include a "no logfiles" commandline option for you.
Can't be that difficult to implement.
--
Kai Antweiler