Feedback, Complaints or Problems

I found out a bit more its google attacking the IE browsers. Well not attacking more leaving simple errors that they know other browsers will autofix but IE would go mental.

Immature but thats corporate minds. I expected it since MS did a fast one over google :P

To the scripting though, is that line

flexTable.getFlexCellFormatter().setWidth(row, 1, "0px"

by anychance?


[Edited by DABhand, 7/11/2012 3:11:22 PM]

That is not cool.

Here is what it says when i open the trainer

Line: 15
Char: 106
Error: Exception thrown and not caught
Code: 0
Url: plusone.google.com/_/+1/fastbutton?url=http%3A%2F%2Fwww.cheathappens.com%2F&size=medium&count=true&hl=en&jsh=m%3B%2F_%2Fapps-static%2F_%2Fjs%2Fgapi%2F__features__%2Frt%3Dj%2Fver%3DTr8Ycv2EZF0.sv.%2Fsv%3D1%2Fam%3D%21-

Works now, so I was right it was a google problem.

at some point we might just create a new trainer manager that skips the built-in browser completely. too many different people have their hands in the browser pot at this point and there's too many different possible formats and etc.

best,
Cal

When you get the opportunity to create a new trainer manager, it would be nice if you also sped up the startup of the manager. Currently it takes approximately half a minute to start up the application on my computer.

That will depend on the number of trainers you have that it has to scan. It has to read the info on all of them and then check the website for updates on them all.

I don't know how the Trainer Manager works, so these are just a few suggestions based on educated guesses..

What if you gathered information on all your local trainers into one request to the server instead of one request per trainer? The status of each trainer should also be cached on the server side so that a db lookup won't be needed for every check. This will give the manager the desired startup performance.

When it comes to the browser problem, it might be an idea to switch to Webkit. Steam is for example currently using Webkit, and it works perfectly for them.

That would be worse, and clog the server up a lot, instead of having 1 small request it could then be hit with a larger problem, then take more time to get the information to send back, and this while other people are doing the same.