#include "quiver.h"

    int q = you.quiver[get_quiver_type()] = get_current_fire_item();

    const item_def* item;
    int q;
    you.m_quiver->get_desired_item(&item, &q);

    if (q != ENDOFPACK)

    ASSERT(q >= -1 && q < ENDOFPACK);
    if (q != -1)

        const item_def& quiver = you.inv[q];

        const item_def& quiver = *item;

        textcolor(LIGHTGREY);

    }
    else if (item != NULL && is_valid_item(*item))
    {
        textcolor(item->colour);
        cprintf("-) %s", item->name(DESC_PLAIN, true).c_str());
        textcolor(RED);
        cprintf(" (empty)");

        textcolor(LIGHTGREY);

    {
        textcolor(DARKGREY);
        cprintf("-) (nothing)");
    }
    textcolor(LIGHTGREY);

    if (you.wield_change)  { you.wield_change = false;  _print_stats_wp(10); }
    if (you.quiver_change) { you.quiver_change = false; _print_stats_qv(11); }

    if (you.wield_change)
    {
        // weapon_change is set in a billion places; probably not all
        // of them actually mean the user changed their weapon.  Calling
        // on_weapon_changed redundantly is normally OK; but if the user
        // is wielding a bow and throwing javelins, the on_weapon_changed
        // will switch them back to arrows, which will be annoying.
        // Perhaps there should be another bool besides wield_change
        // that's set in fewer places?
        // Also, it's a little bogus to change simulation state in
        // render code.  We should find a better place for this.
        you.m_quiver->on_weapon_changed();
        _print_stats_wp(10);
    }

    if (you.quiver_change || you.wield_change)
    {
        _print_stats_qv(11);
    }
    you.wield_change = false;
    you.quiver_change = false;

void print_overview_screen()

std::vector<MenuEntry *> _get_overview_screen_results()

    return overview.show();
}

void print_overview_screen()
{

        std::vector<MenuEntry *> results = overview.show();

        std::vector<MenuEntry *> results = _get_overview_screen_results();