lol, you got on late in the game.. poor gm9 has practically been the only tester for a while and has had to suffer through some good ones lol.. (not going to say any thing about his mysterious eq2.ini bug)

Would a timer like pop-up thingy that gave you like 5 sec or more to cancel before launching work?

or

Should I not have it terminate on launch

or

Insert idea here..

Yes I have an idea!

it should be like 5-10 (probably 10 just in case) seconds delay till auto launch. Something like this example should come up when the updates are done:

***NOTE: I'M SURE you can find some better wording than I***

lol I'd like to know about it, but I guess I'm the "polisher".

too bad he suffered, if I knew about this earlier I would have said something so we could both share the grunt.

drago.

Hehe, I like how it is my bug now. We both know you secretly fixed it. :p

And drago, you don't want to know how it looked like before the "polish", really not. I've been his spell checker for a long time now. ;)

You should take a break, I don't want to spoil your vacation from this. I seriously would like to know about this "mysterious" eq2.ini bug i've been hearing so much about.

Right, while I was happy to help Landiin out since it is a great project he is having here, it is good that you help as well now. To give you an idea, I just checked and I've been poking holes into his builds since February of this year.

ouch, just think....you made it happen!

I have so much free time now, so I'm always available.

drago.

ROFL.. Really though I probably did fix it inevertently but I never found what was causing it or reproduce in on my end.. You sure you wasn't on vacation in Jamaica during that time?

I wish. But good idea, how about sponsoring a trip to Jamaica for your long serving beta testers? :D

Hmm must of lost signal.. :eek:

Build 1.3 (so sleepy)

• Corrected all the spelling errors that have been pointed out. maybe..
• Added a shutdown timer. 10 sec to stop.
• I've lost track of what I did, I stopped editing my did log about 2am:/
• Had to revert back to a save I did at 1am because I guess I was typing in my sleep. LOL j/k:nana::nana:

so how is this timer working? i clicked "Close eq2 companion on run?" and it wont do nothin and unchecks when I exit

and it says "Close eq2 companion on run?" when it should say "Close EQ2 Companion on run"

lol...

drago.

is it working for you gm9?

drago.

So how did we get from here:

to here:

in mere hours...?! :p

The setting is still active, I just forgot to show the check box checked when the app is reloaded. *fixed now BTW, just waiting on more reports before I post another build*

The way it works is..

If 'Close EQ2 Companion on run' is checked when the auto updater is done it'll pop-up at count down dialog. with 3 options on it. Run EQ2 and Close EQ2C, Run EQ2 and don't close EQ2c or Don't run EQ2 and don't close EQ2C. You have 10 sec to decide before it performs the default, which is Run EQ2 and Close EQ2C. You will ONLY get this dialog if you have previously checked 'Close EQ2 Companion on run' and run EQ2 is triggered via the auto-update process. If you click RUN EQ2 button you will not get it. As it figures that is what the user wants or they wouldn't of clicked on the run eq2 button.

That's what I did and nothing happend. I clicked close eq2 companion on run and nothing popped up

hey you know what gm do you wanna die?!?!

drago.

In order to see the pop-up the following settings have to be met.

Settings->AutoRun after updates.Checked = True;
Settings->Close EQ2 Companion on run.Checked = True;

And

EQ2 is being ran from the auto-update process. If you click the button you will not see the pop-up.

I guess I should add a master auto-up switch in settings. Yea think I will, that way you can stop it from auto-updating no matter the settings of the individual models.

P.S.

Some testers you guys are... The C2CCode was overriding the buttons so what ever the user changed on the premade buttons got overwrote.. WTF I had to find this bug on my own! lol J/K BTW, you guys are doing a super great job and I thank you all very much.

those are all on and the launch pad comes up but i see no popup and eq2 companion doesn't close :(

drago.

It dosn't pop-up a dialog before it runs everquest?

nope, but it auto runs and updates fine -.-

Build 1.3
 

Build 1.3 Change Log

• Made major internal changes to:
  • Player/Group C2C model
  • Raid C2C model
  • As a result you will need to delete the following files:
    • eq2ui_eq2c_C2CGroup.xml
    • eq2ui_eq2c_C2CPlayer.xml
    • eq2ui_eq2c_C2CRaid.xml
• Added a Shutdown Dialog window. You will have 10 sec to choose from 3 options. The options are:
  • Run EverQuest II and Shutdown EQ2 Companion (default)
  • Run EverQuest II and do not shutdown EQ2 Companion
  • Cancel All
• Added a EQ2 Companion group in settings. The new group has the following options:
  • Allow Auto Updating. (This is a master switch, if it isn't checked nothing will auto update and EverQuest II will not run with out pressing the run button)
  • Close EQ2 Companion on run

I think that's all.

dragowulf, this isn't the same build from earlier.

ok, I'll try and see if I get any errors and what not.

I don't know what this is, but I've gotten it ever since you did the last update yesterday w/ the popup window.

As I'm waiting for EQ2C to auto run EQ2, bada boom!

***NOTE: This doesn't happen every time I run EQ2C, it only happens sometimes***

Build 1.4
 

Build 1.4 Change Log

• Added a more detailed catch all error handling routine.
• Improved error dialogs.

Exactly what does "Improved error dialogs" mean?

Does it mean you improved the rate at which they happen?

man i love to mess with you guys.

drago.

ROFL.. That is quite possible!

It should give what class is causing the error and what the error is and if it is a error I am trapping it should give show a SL number that tells me what block of code it is in.

Are you still getting that error you was getting a couple post back?

I haven't seen any as of yet.

drago.

I think it's almost ready for public beta

drago.

Unhandled errors:



I had some more actually, but that should be enough. While the "EQ2I News" tabs works fine everything else throws an exception, resulting in the Settings menu being permanently disabled.

Might be due to having a http proxy configured.

I found a typo on gm9's image post

It's occured...not accured :)

lol.

I have not encountered any problems yet, and haven't seen that yet, I can access the settings fine

When did you get these errors and did they happen every time at the same point? Unfortunately address 0 is no help.

I don’t see using a proxy causing this; you would have got a connection error if that was the case I would think.

I started the application, chose the EQ2 patch, saved it. Until that point everything is fine. When going to settings and selecting EQ2MAP the first error occurs as soon as I click ok. The second error then occurs each time I restart the application.

When I select interfaces I get a connection error, which is why I thought it may be proxy related. But as I said, the "EQ2I News" tab works fine (because it uses an IE control). I don't think you really need proxy support though, I don't think anybody would be playing through a proxy.

Ok thanks for that info. I'll start trying to reproduce it.

To late lol already added after your other post. I've been meaning to add it any way. Its not like its a ton of code. maybe 20 short lines at most.

Sure, I made Kaldran add proxy support to ours as well. :)

You missed "EAccessViolation" and "accurded".

I'M SORRY gm9, but the only reason is because I woke up at 4 a.m.

drago.

apology accepted (LOL!)

Thought so...lol

(i also went to bed at 11:30 p.m.)

drago.

Pfft, You should have two bug finding hounds keeping you up all night..