There isn't another reply.
[(D)isplay again, Go (B)ack, (R)eply, (X)it viewing]
[De(L)ete Post/Replies, Dele(T)e Entire Thread, (E)dit post, (M)ove]
>thread 1
Thread being deleted. Exiting from from view mode.
Entire thread deleted.

Ya.. thanks! You shoulldn't have had the moderator features *L* stupid function only returning true *grin* Fixed now!

Complaints:
-- I got lost easily.  I got lost in the 3-post 'Bored' thread, because I
didn't know where I was when I was viewing replies. Maybe make it, when you are viewing replies, have the original posts and/or previous replies above the
one I am viewing and the next ones below.  I.e.:

Ya. I'm trying to figure it out. I'm thinking about showing an entire thread, but, well... I think that'd get far to spammy. Maybe I could just show to a certian depth.

Suggested enhancements:
-- Color-differentiate visited threads (board-level)--maybe bright white for
new/unread, gray for already-read (not an easy task)

I think I get this. You mean when displaying the thread view some differently? Expand alittle. But I think I got it, and nah, not hard at all. I already got read/unread threads in there via id numbers.

-- When exiting a thread, display all the available threads in the forum, saves
me from having to type 'thread view'.

I don't get this one either...

-- When I do:
--> thread 1
Your current thread is set to: Bored.
<<do an automatic 'thread view' for me here>>

Great idea. Done and done.


-- When viewing threads in a board, I should just be able to type in '1' or '2'
to switch threads.  Much easier.
Another great idea! Done and done.

-- Also, when in 'thread' mode, I hate having to type in 'thread <whatever>'. Pure laziness on my behalf, but it's 7 more letters than I want to type. Ever
thought about creating a 'menu' type system for commands?
i.e.
*****************************************************************************
struct pc_data
{
    ...
    DO_FUN  *in_cmd; /*What function/command are we in*/
    ...
}

Then, somewhere in interpret(), add:
ch->pcdata->in_cmd = cmd_table[cmd].do_fun;

Or, better, in functions that will be 'interactive', set it yourself:
void do_buy(CHAR_DATA *ch, char *argument)
{
    ch->pcdata->in_cmd = do_buy;
    ...
}

Don't forget, though, each interactive function will need some way to exit for
'normal' interp.

In interpret(), somewhere above the above, there'd be a check, something like:

if (ch->pcdata->in_cmd)
{
    (*ch->pcdata->in_cmd) (ch, argument);
    return;
}

Or, better:
if (ch->pcdata->in_cmd)
{
    do_function(ch, ch->pcdata->in_cmd, argument);
    return;
}

Excellent idea. I'll whip something up later.

Davion

_________________________________________________________________
Free yourself from those irritating pop-up ads with MSn Premium. Get 2months FREE* http://join.msn.com/?pgmarket=en-ca&page=byoa/prem&xAPID=1994&DI=1034&SU=http://hotmail.com/enca&HL=Market_MSNIS_Taglines


Reply via email to