Hello Everybody.

The forums are moving to a new server on Aug 17.   The previous hosting provider was bought by another and thus they are moving infrastructure.    The forum software and database will be moved ( along with the bug tracker ) to a new host.    I am in the process of testing the new software on the new server now with a test data load from the forums.   

The only issue that I have is getting the DNS updates done so you might have to go to the main PlaneShift website for the next little while to get the ip address of the forums until I get that sorted out.

Thanks,

Testing

Ok, so we last left off we were looking at the psUserCommands::HandleCommand to see how it handles the /dig that is subscribes to.  So looking through this function it has a case for /dig and builds up the network message to send to the server.

psWorkCmdMessage work(cmd);
work.SendMessage();

So taking a look at the psWorkCmdMessage definition I can see that this is a network message ( psWorkCmdMessage : public psMessageCracker ) that is used to send work commands to and from the server.

It has fields for the command, player, filter ( ie what we are 'digging' for ) and a repairSlotName ( which must be used elsewhere ).

The SendMessage command hands the data off to the static MsgHandler to be handled by the network (  msghandler->SendMessage(msg);  ).   I probably won't go into the details of the networking stuff because networking stuff is convoluted as it is.

But basically I now have a full path from keyboard entry, how it is passed around the GUI elements and how it ends up in the command handler and packaged up for delivery to the server.   

So now inside the pawsChatWindow::OnKeyDown,  it handles the CSKEY_ENTER as well and calls a member function: SendChatLine() which in turn calls cmdsource->Publish(textToSend).

Looking at the pawsChatWindow header I can see that it inherits from psCmdBase which has the CmdHandler cmdsource.   So it's basically publishing this command to the CommandHandler to send out to its various subscribers. 

So the question becomes now where does this command handler get created?   By looking around a bit I can see that the psClient engine creates one main command handler.

\PlaneShift\PS\src\client\psnetmanager.cpp psNetManager::Initialize() is the actual place where it does 
cmdhandler = csPtr<CmdHandler> (new CmdHandler(object_reg));

This CmdHandler is then passed around to the various components on the client like the ChatWindow. For example when the pawsChatWindow is doing it's PostSetup it gets the CmdHandler from the psengine itself.
...
bool pawsChatWindow::PostSetup()
{
    if ( !psCmdBase::Setup( psengine->GetMsgHandler(), psengine->GetCmdHandler()) )
        return false;
...

So there is one global command handler that we publish stuff to.




Adding in a hacked together class diagram to get an idea of how the classes relate to each other.

Found pawsEditTextBox in  PlaneShift\PS\src\common\paws\pawstextbox.cpp  and pawsEditTextBox::OnKeyDown(...) looks like a good place to start. Since the /dig command ends with <Enter> this is probably the place to go.   So looking through this function there is stuff to handle the delete key, arrow keys, backspace, nothing to handle the enter key though yet.   It looks like it punts this back to the base pawsWidget class and calls the base pawsWidget::OnKeyDown instead.  So off to that class to see what it does.   

I've deleted the spam tasks and comment that I could find.  Let me know if you find any more.

Questing sucks and it's very boring. So is crafting, mining and training. Even RP, you will find those snobs who will label you. I really just go on ZP to chat or to duel. Occasionally I train, If I have nothing else to do.

I have some ideas on crafting but I want to flesh them out before I approach Talad with them.  Since my time is rather sporadic I would rather have a plan together first. 

This topic has been moved to Forum and Website Discussions.

http://www.hydlaaplaza.com/smf/index.php?topic=40276.0