MacroQuest64

You want me to email you a copy of the latest dev source Lax? One that includes Plaz's diff from the 25th as well as this source?

Sure eqsynapse at hotmail dot com

I won't be able to test until I get home from work, they don't have enough licenses of VC++ for me to compile here

I did make sure to have everything from the newest zip in my source before posting also

Just asking questions so I understand - This window is writen too without using EQ write routines? Is that the correct understanding? Cause if the text still goes through the normal eq pipe and into logs I wouldn't think this buys anything as far as keeping the gm /report command from seeing it.

As I said just trying to understand what's happening here

I can't compile from work either (note to self, fix the damn CD-ROM so I can load my compiler). Emailed you the zip though. Post fixes and I'll get them in so this thing will work.

Just asking questions so I understand - This window is writen too without using EQ write routines? Is that the correct understanding? Cause if the text still goes through the normal eq pipe and into logs I wouldn't think this buys anything as far as keeping the gm /report command from seeing it.

When /report is used, every chat channel that the chat manager knows about returns the visible text (or perhaps more if they want it?). To avoid this, we let the chat manager create a chat window as normal, but then remove it from its list. The chat manager no longer looks in this window for a /report.

The old WriteChatColor used a function that went through the standard everquest "display chat".. what that did made the chat STML safe, used a user-defined color and window filter, called the chat manager's "add text to chat window", and logged to file. With this new system, we do none of the above. The system is based on the "add text to chat window" code used by the chat manager rather than the encapsulated display chat command. So it's going directly to the window and appending the stml, with whatever colors wherever we please, and does not appear in the eqlog.

Don't worry, this is thought through :)

btw, i just tried compiling in vc6 and like someone said, it doesnt compile staright away, but it was kinda easy to fix so im cvsing it, and lets cross our fingers... as always Lax... GREAT WORK!!!

ok cvs and zip updated

THIS TOTALLY ROCKS! IT LOOKS SO SWEET! SO AWESOME I AM NUMB! HOLY @#$%#$% COW!!! :)

Thanks for the save EQMule. Would have been another 4 hours before I got a chance to look at it.

Ah good, I knew it couldn't be something too difficult to fix.

I eh didnt update the macroquest.sln since i dont have vc7 installed, but wassup was kind enough to do it, so I updated the zip and the cvs, now our vc7 users will be able to compile it as well

oh Lax... sorry to say this, but I ehrm think we might have a problem... I want you to download the zipfile, compile that code and just let your char be logged in for a while, dont have to do anything... I was just sitting quietly in pok, and boom crashed, took about 30 mins... not sure whats going on, could be the new chatwindow, or something else, we have had a few different cvs thingys going the last couple of days, but since I havent made any of thoose changes just been the middle man cvs ing it in, I dont really feel like getting the microscope out if you know what I mean :)

I'll take a look when I get home. I left my char in for a while last night and didn't have any problems...

Worked great for 30-45 minutes, then my EQ Client just froze, but no CTD.

I couldn't alt-tab or get the task manager up either. I had to reboot.

I'll venture a guess that it's crashing when the amount of text in the window is more than it's supposed to handle. I'll figure it out

Is this just randomly crashing after that amount of time? Is the window getting a lot of use? Will have to put in some debugspew to figure it out.