athomsen

drscouse, you are correct. They are not removed. I have posted here before that leaving these settings on your computer is CRAZY. This is especially true for network admins that use WPI (read stupid end users). Personally, I do not use the reg file, but I do not use WPI with fresh SP2 installs either. Nor have I tested it.

Dennis, everything you mentioned are known issues/requests and are being worked on. Thanks for the input!

A friend read this and thought that this comment that I made did not come off as I intended: It is probably because I wanted to kill someone at Verizon when I wrote that, but that is a whole other story. I would like to clarify that what I meant to say was that the code is screwed up but that had to be expected when there is a community of "non-programmers" working on a project with little to no documentation for a long period of time. (By documentation I mean for the programmer) Sorry if I p***ed anyone off. I'll cool down before I post next time

AlBundy33, everything you posted is a great idea and in fact I have already thought of them too. I am rewriting WPI because quite frankly as you have noticed with many different people making changes the code has been butchered. (no there is no eta on me being finished) Besides that I am brining it into the 20th century and using classes. Oh yea... I have mentioned this before but some of those reg tweaks are DANGEROUS esp in a network environment. I have not tested if they are required but kel the are on fresh installs. One of the things I have already done is to move them all to WPI and have them removed when it is done running. I am going to make the cmd file disappear come hell or high water.

You can just use reg before or after to run a reg file. Behind the scenes WPI will add REGEDIT /S for you.

Here is the cmd file I use. All it really does is map a drive. @ECHO OFF REM Map network drive since we can't use UNC paths net use X: \\server\share /persistent:no REM Determine the WPI startup path. REM if wpi should run off the cd the replace %~dp0 with %cdrom%. set wpipath=X:\WPI_4.3.5 REM Hide this command window. %wpipath%\Tools\cmdow.exe @ /hid REM Special registry tweak needed. regedit /s "%wpipath%\common\wpi.reg REM Make WPI directory the current directory. for /f "delims=: tokens=1" %%i in ("%wpipath%") do %%i: cd "%wpipath%" REM Start WPI and wait for its end start /wait %windir%\system32\mshta.exe "%CD%\wpi.hta" exit :end Then when you enter the path to in the command textbox in the config wizard you can use \\server\share\somthingelse\anotherthing\me.exe. So, now you can spread your files out over a billion servers WPI won't care. This meets all of your requirements and does not require any mods to WPI.

Best I can figure here is that when you are adding a program you are not giving it a program name. WPI depends heavily on that name. if this is not the case post repeatable instructions for adding a program. You can remove this error by changing this line in check.js var oldcat = cat[1][0]; to var oldcat; But then your programs will not display anyway because there is no program name.

OK, to fix the number in category issues replace this function in check.js. I have only tested this briefly. If some of you would like to try and break it that would be great! // Returns if check box is for a category function isCategory(i) { //alert(i + "," + typeof(i)) if(typeof(i) == "number") { return false; } var numbers = " 0123456789."; var isString = false; var char; for (var j = 0; j < i.length && !isString; j++) { char = i.charAt(j); if (numbers.indexOf(char) == -1) { isString = true; } } //alert(isString) return isString; } Also, oneless could you send me / post your config with the hide program thingamabob. I am not totally sure how you are hiding the program.

Don't suppose you could post this as a file. Would make life easier for me to try and fix it. TIA

I really do not understand this entire topic. Why not just enter the network path as the command. No complicated addtions needed. EDIT: BTW network paths were fixed in 4.1

I have school tonight but I will work on it on Thursday.

Kel put a rush on making the combo optional so I did so today. It just has to go through testing and his final approval.

Sorry there are no files up yet. My PC bit the dust this morning. I will try to get them up on Monday from work.

Actually I do not (my 4.2 was morphed into the next version). I will make the changes to a virgin copy of 4.2 and post the files tonight.

I guess that it is the background you want to fix. Look here: category fixes topic. You inspired me to post some overdue changes to the forum. One of them includes a fix for this. Note: You must make ALL changes for it to work. The category selection function in that topic is fundamentally different than in the official release. EDIT: horrible grammar

OK, I wrote this stuff awhile ago but we were gonna wait to release it. Then some pretty ambitious mods were taken on and well, no new version is out. I take a large part (OK, all) of the blame for this since my ambition was/is slowing everyone else down. BTW, my ambition currently = rewriting all of the WPI code to make it more efficient as well as object oriented. (How does cutting config load times by, well... more than half sound?!) Enough blab from me here it is. Use at your own risk. In other words, I will probably not be fixing bugs if there are any. Things that these changes fix or add - Removed duplicate check(all) from select all button - checkCategory is written WAY better. It integrates better with the rest of WPI's code and it should run faster. - Fixed multi column selection issue with categories - Improved use of exclusions when working with categories (for now, could be better) - Category text is now clickable just like the program text - Category div does not surround all checkboxes (like in pre 4.2) Decided to post as a file to preserve my pretty tabbing Change_Log_2005_08_05.txt

Thanks for the vote of confidence there g-alex You're welcome!

Well, if you have 2 different installs with seperate settings then set the exclusion for prog1 = prog2's UID and the exclusion for prog2 = prog1's UID. Now the user can only select 1 at a time.

I am guessing from your title that you just run a registry file to change the setting. If so, you can have one program entry for the install and another entry for the reg file. Then make the program entry for the registry file dependent on the program install. This will prevent someone from running just the registry entry.

This will work on any element that raises the onfocus event... like checkboxes. For those you will have to go into boxes.js and look for where the checkboxes are created.

The only way to remove this is to call blur() when the onfocus event is fired. This however will prevent you from using the keyboard to navigate WPI. If you want to add onfocus="blur();" to the link element.

Mysteriously the HTML portion of WPI has gone from about 350 lines to about 280 lines. Wonder what that means...

Ok, is is tonight and I am not done yet. Since I had control over wpi.htm I have taken it upon myself to updated the hell out of it so this is all taking me longer than I expected. almulder I will contact you via IM...

I am working on this. I have a previous engagement this morning for a few hours, but when I return I will jump right back into it. Will have something for you this afternoon/tonight. And, your welcome. UPDATE: I have gotten most of the basics working. Making these changes allows us to move all the HTML back to wpi.hta. And because we no longer have to read and output an entire HTML file WPI runs WAY faster. Only problem is that all this does require making some changes to the HTML and kel told me that he made some changes so, I am going to ask him for a copy so that he doesn't have a nightmare making my changes. Time for me to go.. be back in a few hours. UPDATE: I just got back. kel was nice enough to upload the file for me. I'll post when I'm done.

I see where this line of questioning is going and I think it is a great idea. However, I do have a suggestion. While changing wpi.htm to write a javascript variable in place of the theme name would work, you are going to need to convert all 47 occurrences into javascript in order to do so. And since not all of the occurrences are close together it will become burdensome, quickly. Instead you can write a function that modifies any tag's attribute that requires theming with the correct path for the chosen theme. Then you could call this function when the body onload event is raised. Another function would be needed to be written for when the mouse events are raised. As long as the image names are similar (which they look to be) this should be pretty simple. Using functions will not require huge <script> blocks and will allow wpi.htm to remain a HTML document rather than a huge js file that creates a HTML file on the fly. Just my 2cents though...