sadicq

Look at the guide you can find here.

Hm... here's my try (but I could be wrong 'coz I'm very dizzy right now) Open tips.js. Search for "+txtTxtAli+" and replace it with style=\"text-align:justify\" Note that this will override the TextTextAlign setting in options. It is just a quick dirty workaround.

Options -> Installer -> Categories Sort Order

IMO, the whole tips.js should be rewritten from scratch. It is really messy and the way it is loaded makes WPI much slower! And I really mean that. Attach a debugger to WPI and see for yourself how the tips are working ... Not to say about the browser compatibilty checks in it ... . I won't cry about pngs and tranparency problems ... but the performance

Silly me. Remove the transparency too (put "" instead of 99).

Ok. found the problem. You have a value of 2 for the ShadowType. That is the only thing wrong there ... try it and post back

Yes .. I get the same effect while the fade in takes place ... after that finishes, everything comes back to normal.

The png fix is not the problem for that. Just tested it and it works fine (well a little bit weird with the fade in though ..., but not the problem you're talking about). I'll look into the timer replacement code ... Edit: No, that is not the problem. I think something else is interacting with your code ... Seems like I can't solve this one... anyway for me the problem appears only for half a second ...

This solves the problem. I had to trick the javascript at this one ... See the attached file. another_one.zip

Sorry for the late reply... (still gaming here ) <script language="javascript"> document.write('<link rel="stylesheet" type="text/css" href="./Themes/'+ Theme +'/wpi.css" \/>'); </script> You missed the language="javascript". I guess it should work now.

Well, shortly, you can't . A transparent iframe is the same with the div... it has no effect. Read the comments in the tips.js and you'll see. And you can't introduce the iframe in the wpi.htm because if you do that, nothing will be visible any more. If a transparent iframe blocks the dropdowns, then, yes you can (I think). But that doesn't happen on my computer.

Sorry pal, this is a gaming night for me ... and I really have no clue . I'll take a look at it though but I don't think I can do much about it ...

This is the fixed tips.js. Replace the one in WPIScripts with this one and everything should work (eh... only the problems reported in this thread). The method used is the iframe one. Enjoy! tips.js

Updated the previous post. Although I rewrote the whole code, I did very few tests with this one, so I expect some bugs to come out ...

IE 7 is definately not a solution. Many users using XP won't update their IE, not mentioning the users who use Win95/98. Although they are old, they are still used in low-budget companies and old home computers. About the iframe fix, that was what I suggested in the link I provided, but I hope I can come up with a better fix. Btw, you should downgrade to IE 6.0 or use a virtual machine to test your files for weird errors that may have been fixed in IE 7.0, but still present in the old one.

I just talked to my friend and he said he can fix this by using another method... which is much better, he says. The problem is that he is really busy with some work today, but if you guys can wait I'll try to get in touch with him tomorrow. From what he said, I understood there's no need to edit anything else than tips.js. And that will fix all the dropdown show-ups.

Now I understand. And I have the same problem, as I said here. Here is what I found regarding this problem: The site where I found it is here. I hope you find this useful.

Well, if I were you, I wouldn't have alerted the user using an "alert" window. The control flashing is enough for most of the users. I've put that line just to show you that is working. You can easily comment it out with // or simply remove it.

So, the wpi.htm file contains a "common" header, right? If this is true, shouldn't it work if he puts the code in the wpi.htm head section? The first time I looked over the code I thought indeed it should work out that way. Maybe I'm just too sleepy right now and I'm making another foolish mistake ...

Well, I have another method and I'll post it here I get home. It was submitted by another member in this forum, but it only fixes some of my images (I don't know why). If I find another method that works 100% then I'll let you know. For me Dumpy Dooby's method does't work at all (I guess I made something that interacts with it ...). About the tooltip thingie, I really don't get what you're saying. *shrug*

Maybe you want a manual from a previous version? It is not 100% accurate for the new version, but you can use it if you have no idea where to start. I have the manual for the v3.8 version (which was the last big step before 4.4 and 5.0, so not so long ago).

Well, I usually don't spam the forums, but I have to say: This looks awesome!

There is no manual for the version 5.0 yet.

Well, silly error from me ... The options tab is created using separate htm files ... But I see no body tag in the common\*.htm files. I think mritter or kel should look at this ... IMO, the WPI code needs the <html> and <head> ... </head><body> tags in configwizardtemplate.htm and the </body></html> in optionswizardtemplate_misc.htm Until they modify the code so it contains all the tags (html, body, head), stick to the method you used. But I suggest you guys modify the code in the 5.1 version so the options view can have a valid structure.

Well, I wasn't sure at the moment I posted and neither am I now. but I think you have to add the init() to the <body> tag in the wpi.htm. <body class="body" onload="init(); SetScriptWaitTimeout(); startstop(); fillBoxes(); check(CheckOnLoad); startstop(); window.focus();"> and link the js file in the head of the same file with <script language="javascript" src="./themes/Glossy/Code.js"></script> I must say I don't fully understand what you are saying with the code you entered in the js ... but html has nothing to do with js files. So I think you should consider moving it to the wpi.htm. It is the best options I see (and the only 100% correct one).