Jump to content

mritter

Member
  • Posts

    1,094
  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country

    United States

Everything posted by mritter

  1. I think I may know what the problem is. Testing as I write.............
  2. I know what is wrong with it. It must have been broken for awhile because 6.4.1 & 6.4 don't work either. I will get'er fixed.
  3. I will look into it.....I thought it already did, but I could be wrong.
  4. Fixed the bugs above and the one with all themes using my euDock not working.
  5. One handy one I just used in a new "example" theme I will be uploading is ExtraHeight. My progress bar needs to be to 60 pixels taller, but only this theme. So, since it is an example, I don't want to permantely change it in Options, so I added it the top with the others; ExtraHeight=60; Now, since I needed this I added some new tags in installer.css to change the height of the progress bar. I don't want to edit the actual Installer.hta code since it will affect all themes. Of course, this has changed all themes AGAIN! My bad, I should have tried this sooner and gotten it out with 6.5. BUT, it is a very easy upgrade 99% of users will never use and not have any headache updating to. Next version......
  6. No, but that could be an option down the road. How many OS's do you use that this would be useful?
  7. All of the themes have been updated to 6.5. At the top are some lines you can change to suit your needs: <script type="text/javascript"> // maxentries += 3; // Set your custom number of items per column TimerWidth=140; // Timer progress bar width TimerHeight=16; // Timer progress bar height ShowPercentValue=true; // Toggle showing the percent value, ie: 75%, in the install progress bar // ShowToolTips=false; // ToolTips must be turned off for this theme. Will not affect other themes. </script> The maxentries is probably the one to be editted the most. If the column gets cut off, do maxentries -= 1; You may have to do as many as -= 3 to get it to take full affect. I left some room at the bottom for the --------- Previous ----------- Next -------- line. Don't forget about that. In fact, anything in globals.js can be overridden by putting the line in the section above. This way it only affects that theme leaving the gobals untouched.
  8. As far as the number of columns go, do you have enough entries to fill 3 columns? WPI doesn't break them up automatically, it fills one column, goes to next, etc. NumCols is the MAXIMUM number per page. One thing I don't like that WPI does is shift the items over 1 column leaving the first one blank when categories are longer than 1 column (carries over to second). Looking in to it......
  9. No, DJPro is somewhat correct. But the proper method is to edit the maxentries line in the theme wpi.htm. In your case, maxentries -= 1; You may have to do up to 3 for it to take full affect.
  10. All themes have been updated to 6.5, including Gnome's. Get them off the WPI web site once Kel gets the site updated (still has 5.5 themes up). If you have a custom theme you want updated, post a link here and I will do it.
  11. Dowloaded it and will get it posted. Mostly it is code REDUCTION and cleaning. Added 2 new timer css classes; centered the <div>'s properly; new sizer() that determines the numbers of items per column automatically; custom theme code call; all in all, just more consistant with all themes for easier updating.
  12. Thanks Dyna! I fixed both bugs and sent Kel a new archive. Total "Duh!" on my part.
  13. First off: what version are you using? I ask because there is no getOSlang() function call. That is why you are getting an error. There is now in 6.5. Try it with new release.
  14. I will definetly add this in the next version after 6.5. I like it!
  15. Added to my to do list. Like the resolution idea.
  16. When I got back from my siesta, I looked at this again, too. I have always wanted sub-items, just never came up with an easy way to add them in the Config wizard. Baby steps, but I have n idea for unlimited commands that will free up space, and maybe give me some ideas on how to add sub-items. I just thought of one idea on how to get more screen real estate, but it will still come down to what resolution each user uses. 1024x768 should be the minimum, 1280x1024 would be ideal. It won't be any time soon, but it has always been on my mind. Then if that is a success, then maybe other types will come afterwards.
  17. Depending on what version you are using, I fixed a bug dealing with that. A space was left out somehow. 6.4.1 may have that fix; 6.5 definetely does.
  18. But 64bit checks will not be included. Sorry. Just haven't had the time yet. There are some bugs that we needed to get fixed, and a new Window feature, before anything else new got added. I am planning, maybe, a Super Update to v7 next. I have a nice list started of new features that will satisfy everyone: updated installer, theme/style editor, registry tweaks (instead of nLite or doing it yourself), etc. I will get ahold of you when I start the 64bit stuff. Seems like no diffinitive answer has been found yet. I have an AMD64, but not using WindowsXP64 so I can't really test it. That's where you will come in. You will have to be the tester.
  19. A question mark means something, not everything, failed in the install. An X means the whole thing failed. A check mark, all good.
  20. WPI doesn't use any libraries. It is pure JavaScript and HTML run via mshta.exe; that is why Internet Explorer can not be removed. It is essentially a "web page" designed to look like a stand-alone program. Either you have some errors in your config file or you have modified some of the files, or if you used nLite you may have removed something required for IE. Try running it on a clean computer, or a friends, just to see if it works "as is". If it does, you know it is something with your custom Windows config. If it does not work, then more information from you is needed. Post your config file here so we can take a look at it. Usually something simple. Or wait until sometime this weekend for 6.5 to be released to see if it cures the problem.
  21. I thought it might come down to reading the css file.....ugh..... Thanks, guys
  22. Does anyone need/use the View Source button? I have no use for it. I don't see why anyone else would. I am taking it out of all my themes. If you have a reason to keep it in future releases, tell me here and how/why you use it, else it will be deleted in a future version.
  23. It's for WPI. .txt is defined in the .css files. Make a <div>, but the content defines with class="txt" later on. I want to see what size the text is of the "txt" class. Maybe thay makes more sense? The problem is, I need to know BEFORE the text is laid out. So, what is the font height of the css class "txt" in themes/wpi.css? I want to know as soon as WPI is started.
  24. I am using a style sheet so I was not having any luck. I can't hardcode the font size in for where I want to use it. Any other ideas?
  25. Does anyone know how to check the font height assigned to a <div>, or anywhere? I need to know how tall the font is. FontHeight=document.getElementById("ThisDIV").font-size; Something like that. That doesn't work, of course.
×
×
  • Create New...