Inventory display bug

[PowerWyrm]

If your character has missiles equipped in the quiver slot and nothing in the inventory, the inventory subwindow will display:

(nothing)
b) in Quiver: n missiles

When using the "i" command, the "in Quiver" line is aligned to the right and out of the screen (because quiver slots are not processed when calculating max name length in show_obj_list).

[d_m]

Originally Posted by PowerWyrm

If your character has missiles equipped in the quiver slot and nothing in the inventory, the inventory subwindow will display:

(nothing)
b) in Quiver: n missiles

When using the "i" command, the "in Quiver" line is aligned to the right and out of the screen (because quiver slots are not processed when calculating max name length in show_obj_list).

Thanks for catching these!

Would you mind opening tickets in trac.rephial.org so we can easily see which ones are still outstanding and which ones aren't? It's easy to lose track of them on the forum.

[jens]

Originally Posted by d_m

Thanks for catching these!

Would you mind opening tickets in trac.rephial.org so we can easily see which ones are still outstanding and which ones aren't? It's easy to lose track of them on the forum.

Is that a general advice? I mean, what I usually do is post an issue to the forum, then let one of you dev guys open a ticket if deemed worthy. Which sometimes leads to me getting ignored and frustrated, and having to keep track of the issues myself to repost later...

Would it be better to open a ticket, then if deemed unworthy you close it? That way I would at least know that I was not ignored, just disagreed with, which is much better for me :-)

[PowerWyrm]

Done. It's now ticket #1465.

[Max Stats]

Originally Posted by jens

That way I would at least know that I was not ignored, just disagreed with, which is much better for me :-)

Huh? Did someone say something?

[Zyphyr]

Originally Posted by Max Stats

Huh? Did someone say something?

Nope. Completely empty thread here.

[d_m]

Originally Posted by jens

Is that a general advice? I mean, what I usually do is post an issue to the forum, then let one of you dev guys open a ticket if deemed worthy. Which sometimes leads to me getting ignored and frustrated, and having to keep track of the issues myself to repost later...

Would it be better to open a ticket, then if deemed unworthy you close it? That way I would at least know that I was not ignored, just disagreed with, which is much better for me :-)

I like seeing forum posts about bugs, and for people who only report a few bugs, it's probably the easiest thing for them to do. But it's nice to also have people open Trac tickets...otherwise I (or someone else) has to remember to open the tickets, and then copy the bug description (or link to the post on oook). Which is fine, it's just nice when someone else does it. Ultimately Trac tickets are more useful because they have a unique ID # that we can use to talk about them, and we can run reports (to see how many bugs are outstanding, to figure out what we fixed since 3.2, to know who's working on what, etc).

I only mentioned it because I know PowerWyrm has been posting about a number of issues (and also happens to be a developer!). I didn't want to miss/forget any of them.

We are committed to fixing all bugs, no matter how they are reported!

[jens]

So basically if I see a bug I can just as well open a ticket for it (after verifying it's not on trac already).

But what if it's a grey area case, where things are working in ways I see as clearly inferior, but others might have another opinion? Then I guess opening a ticket must be done after some discussion. The problem is that if it is a minor issue often there is no discussion, or no resolution to the discussion, it just ends.

[Magnate]

Originally Posted by jens

So basically if I see a bug I can just as well open a ticket for it (after verifying it's not on trac already).

But what if it's a grey area case, where things are working in ways I see as clearly inferior, but others might have another opinion? Then I guess opening a ticket must be done after some discussion. The problem is that if it is a minor issue often there is no discussion, or no resolution to the discussion, it just ends.

If you read http://trac.rephial.org/wiki/TicketCreation, you'll see the advice to open a ticket after your bug has been corroborated by somebody else on Oook: "Please do not open a ticket unless at least one other person can reproduce your bug". This way we will avoid a lot of non-bugs being opened on trac.

[jens]

OK, I'll keep hassling the forum until I get a response on an issue, then open a ticket ;-)