mritter

That's probably just a font size problem. Go into wpi.htm of your theme and search for <!-- Buttons bar --> Above it lower the height %, and down lower find <!-- Timer --> and increase it's % accordingly.

Added JuMz's idea. The UID is now only changed/updated if UID is blank, as in, a new entry. This will help with version updates. jellobui: Added youd idea for the install order next to name.

The new installer put control in our hands, not that of Windows and GuiRunOnce. It has its advantages and disadvatanges. Mainly not being able to restart the computer and pick up where you left off. The good side is that we have a log file, progress bar, visual que of fail/success, etc. I have a note to try and get a restart possible. Maybe some day......

@soporific 1400x900......not bad. But I have 3840x1024. Matrox Parhelia spread across 3 17" LCD monitors. If I had the desk space I would get the newer card and add a 4th monitor.

I added this in to 5.3 minus the color highlighting (for now). I like it.

I have been continuously updating the themes files since I started using WPI back in v4.x. The problem that arises with each new version is that I incorporate user suggested ideas, bug fixes, my ideas, code improvements, etc. Sadicq has sent me several updates that I still need to merge in with mine. I can say that it is coming to an end. An end until Almulder releases his appearance editor. This will HOPEFULLY standardize the themes to a point where updates will not affect your themes. I can't promise you no more changes/updates to the themes. v5.3 will have some more. This was inevitable. I really hate to say this, but: hold off on making new themes for a short while. Progress is moving along at a break-neck pace, but HTML code is not as forgiving as JavaScript. I am just wrapping up the MAJORLY updated Options wizard, which does not affect the themes, yet, but may down the road. Config wizard if next. Like I said: most updates are from user submitted bugs and/or ideas. Don't be mad at me or Kels for the changes.

Debug Mode is gone. Still waiting on a 2/3 vote for Show Source.

Line 1644 is in the saving of the useroptions.js file. The function name has nothing to do with the line number. What are you doing when this error comes up? If you are using your old 1.2 useroptions.js file, then that is the problem. They are not compatible. Try renaming it so you don't lose it, then start WPI again, go in to Options, it will save a default set. Close. Open again and try to reproduce the error.

Kels got a little ahead of me on releasing this version. I have some new ones I will be posting soon which will help alleviate some space issues on 1024x768 screens, give some fresh ideas, and new looks. Stay tuned......................

I have been trying to think of a way to get the whatfunc variable to return to the previous calling function for some time now. The last call of every function could be to set it back, no problem. The problem that arises is that for every return call it would have to be set back there as well. Would add a lot of lines. The same would have to happen for position variable. If there was a way to check/catch when leaving a function, by getting to the end or a return, then it would be easier.

I have all the known fixes worked in to the latest 5.3 beta. Sadly, when I was testing with other people's config files I found a few more errors not yet reported. Mostly cosmetic but still a bug.

I am giving the Options wizard a MAJOR overhaul, followed by the Config wizard, and need to decide on some dimensions for the "window". I need to know how small I can make it and still be usable with different languages. What resolution is your desktop when you are editting your config? Not the resolution after installing Windows, reboot, and WPI starts. What is your normal everyday working resolution.

Does anyone still use the Debug Mode or look at the source code with Show Source button? I feel they are fast becoming obsolete and should be removed. But if anyone still uses them, post here so I know and will leave them in.

In core.js make sure the Pause() function is like this: function Pause(secs,milli) { position="core.js"; whatfunc="Pause()"; var SleepShell = new ActiveXObject("WScript.Shell"); var duration, sleepCmd; duration="-m " + ((secs*1000)+milli); sleepCmd=wpipath+"Tools\\Sleep.exe"; SleepShell.Run('"'+sleepCmd+'" '+duration,0,true); } The duration line had an issue earlier.

That will be fixed in next version. Should have been added right away. Won't have to Save first.

Already talked to Sadicq about his ideas. Keyboard shortcuts: I tried some a few weeks back but could not get all to work. Still have it on my to-do list.

DIRCOPY is the built-in command. Use DIRCOPY like you would %CDROM%. If you are not using it that way, base your command line on this: DIRCOPY gets replaced with: CMD /C xcopy /I /E /Y ....... CMD /C opens a command window.

There are now Pause and Abort buttons in the installer. I wanted that from day one but had code problems. Dje figured it out. 5.2 will be out soon to cure the installer problem and some new features.

Technically, %cdrom% will work everytime. All it is based on is where it finds wpi.hta or win51 or i386\driver.cab. So if you launch WPI from your removable drive, it will find it. %wpipath% could actaully be worse in your case. if you embed WPI in sub-directories and have the installers out in the root, then %wpipath% will be wrong. Stick with %cdrom%.

If you mean reschange, then it is in the tools folder. Go to Options -> Tools and set the resolution you want.

Solid, Every theme, old and new, has layerconfig it in. It better or you would never see the config wizard and WPI would crash. You want to be searching in wpi.htm not configwizardtemplate.htm. (I hope I didn't say that in my original post)

The problem people run into with themes on different resolutions is that they try to use 1 huge wallpaper image and try to line everything up based on their current resolution. As soon as you switch, or someone else with a different resolution uses it, the wallpaper gets scaled up or down to match. This throws off all the visual alignments. The best way to avoid this is to keep using the table that Glossy is based on. Put your title up at top, the bottom bar at the bottom, and your wallpaper in the center <td> frame. Then only the widths will be changed, not the heights, of the top and bottom bars. The main display will scale x,y but should affect how the MediaPlayer blends in, for example. So, if you line up elements vertically then you can not use one huge wallpaper. Break it up into pieces and use the table.

The abort feature has been on the drawing board for quite some time now. Just recently the installer has been updated to have a Pause and Abort buttons. Stay tuned for that.........in final testing stage. The tool tips in the installer: I doubt it. If you don't mind using extra space for a text box to show the tips (not a true tool tip popup), then possibly. But not reallyh necessary since it is supposed to be "unattended". I am not sure what you mean in #3. More details.

Is anyone using the stopwatch in debug mode? It is worthless now that I have updated the Config wizard. I am planning on removing it to make the timer code smaller and for future upgrades. If anyone is still using it let me know now and I will see what I can do.

I have never had a problem with mshta.exe not launching WPI direct. If you do, do something like this in your .cmd file: mshta.exe wpi.hta That will launch it.