Jump to content

mistaecko

Member
 View Profile  See their activity

  • Posts

    2

  • Joined

  • Last visited

  • Donations

    0.00 USD 

  • Country

    Thailand

About mistaecko

Profile Information

  • OS
    none specified

mistaecko's Achievements

0

Reputation

  1. mistaecko
    Thanks, I've seen those. I will try in the Unattended XP forum though, hoping that they will not bash me for asking noob questions (even though I think it is a valid question considering that so many tools are outdated). mistaecko
  2. mistaecko
    Found it!!! Now help me understand it It is related to the layers (DIVs) and how they are cascaded, more exactly how the background image is implemented: I made the following changes in \Common\Themes\Windows\wpi.htm (thanks DJPro for pointing me there): 1. I basically removed the bgpiclayer DIV. In order to avoid JS errors that try to work on the layer I just added an empty DIV with this ID just before (outside!) the wrapper DIV. 2. Moved the TipLayer DIV to outside the wrapper DIV but BEFORE the bgpiclayer DIV. Positioned AFTER the bgpiclayer DIV this will NOT fix the problem. <body class="body" onLoad="WPIReady();" onClick="stopInterval();" onKeyDown="stopInterval(); CheckKey();" > <object id="dlgHelper" CLASSID="clsid:3050f819-98b5-11cf-bb82-00aa00bdce0b" width="0px" height="0px"> <!-- For list of fonts --> </object> <div id="TipLayer" style="visibility:hidden; position:absolute; z-index:1000; top:-100;"> </div> <div id="bgpiclayer"></div> <div id="wrapper" style="position:absolute; width:100%; height:100%;"> <div id="div_logo" style="position:absolute;"> Voila! Problem mostly gone! But background as well! I think the main problem is how the background image is applied. Why not use the CSS background property on the wrapper DIV? <div id="wrapper" style="background-image:url('../Themes/Gnome/Wallpaper.jpg'); visibility:hidden; position:absolute; z-index:-4321; width:100%; height:100%;"> This worked well for me (in the above code) The flickering (repaint) still happens when hovering over the Exit button, and when switching tabs in the windows (and on some other occasions). The hovering code can be improved as well, because now the tooltip flickers when moving from the icon to the text, because there is a gap inbetween and IE will trigger the onMouseOut/Over events in that case. For an explanation and a possible fix, see here: http://dynamic-tools.net/toolbox/isMouseLeaveOrEnter/ I am not a HTML guru (far from that - I'm programmer), but I've worked with some, and to me it seems the HTML code might be able to be improved by following recent 'standards' in web design. Tables are out nowadays, DIVs are the way to go. Main reason is that tables should be used only to structure data, not as layout tool. And while this is more relevant to websites and not necessarily to a tool like WPI, I guess it is still 'best practice'. I'm not sure but I think there are technical reasons as well. I think that there are issues with nesting DIVs inside a table TD, which I've seen also in the WPI code. Furthermore if you use a strict DIV layout and format only via CSS, the end result will allow for easy skinning! So my recommendation (obviously NOT based on expert knowledge ): Get rid of background images applied via <IMG> Get rid of tables Move CSS style attributes from inline code to CSS files. mistaecko
  3. mistaecko
    I just toyed around with the code for an hour or more - I'm still pretty lost in the code, and having never worked on a HTA before I had to fall back to most primitive methods for debugging. First of all, I don't have a solution, not even close However, I think it is important to track down the exact problem first, then the solution will hopefully be obvious. IMHO it is important to stress what DJPro has already pointed out: the flickering is NOT really related to the Tooltips. Even with Tooltips disabled the flickering still occurs on at least two different occasions: 1. Hovering over the Exit button. 2. Loading the config, options, themes, etc Windows will cause the menu flicker as well. ad 1. This might indicate that the problem is related to onMouseXXX events, either defined on the Exit button (or one of its parent containers) or on the menu panel (or one of its parent containers). To me it looks like it might be the onMouseOut event of the menu panel or the main window. ad 2 Switching a panel inside any of the opened windows will trigger a menu flicker. This might indicate that ANY component on top of the main window that holds the menu will cause the menu to flicker. I guess that also applies to the tooltip windows, and since those are repositioned continuously the problem is just so much more obvious. I further assume that the flicker is a repaint of the menu panel. The repaint might cause the tooltips to disappear, moving the mouse will adjust the position of the tooltip and trigger a repaint of the tooltip layer. The behavior is more clear when hovering slowly over the Exit button. The menu repaints and the tooltip appears. My guess is that the menu repaints as a result of a onMouseOut event of the menu panel, and the tooltip appears as a result of the OnMouseOver on the Exit button. I would also consider a bug in the dhtmlx framework/components, and ask for feedback in the forums there. I found one problem related to repainting/flickering related to an embedded .NET component. Seems worth pointing out since a HTA is clearly no 'clean' web application, and related to Microsofts ActiveX and component architecture (maybe?). http://forum.dhtmlx.com/viewtopic.php?f=5&t=12087&p=35328&hilit=flicker&sid=a20820412394c16ee3473de08b00c830#p35328 If I had any more clue about the WPI app and/or debugging HTA applications I would try to pin down the problem even more. I guess somebody who has the layout and component model of the app in mind can pick up from here. A good option IMHO would be to strip the application bare of component by component as long as the problem exists. Either ending up with a very basic component layout that makes it easier to understand and debug the problem, or maybe even fining the problematic component/structure. Sorry for the lengthy post, and if I just pointed out what you guys already knew anyway. This is my effort at contributing to this great project and saying thank you! mistaecko
  4. mistaecko
    Hi there! Found myself in the need of creating my own Windows XP boot CD - kind of awkward since we have 2010 and Windows 7 saved us from Vista quite a while back.. I get kind of a sentimental and depressed looking around the XP sections - many have moved on and tools have been abandoned. Thanks for keeping the older forums up and running though! I wonder if this is the right place to let my noobness hang out and ask if anybody is willing to give me a short feedback on the state of XP slipstreaming/modding. I did quite a lot of reading during the last couple of days, still I wonder which is the way to go nowadays with XP's glorious days being over. Both nLite and RyanVM are no longer maintained, but both should still do the job, right? RyanVM's update packs are no longer maintained, but others jumped in and now there are 2 or 3 update packs for XP post-SP3. Tried the one from USER_HIDDEN with RyanVM first but ran into troubles, then switched to nLite and was successful. I assume both tools should still work. Currently I am sticking with nLite - I remember reading somebody recommending RyanVM for service packs, update packs and addons, then use nLite for tweaks. Then use DriverPacks last. Obviously this person thought RyanVM is better at integrating additional stuff, not sure why. It seems nLite does not well at removing previously added addons. For now I am using nLite because it worked for me so far. WPI is an alternative approach that allows installation of software, registry teaks, etc AFTER installation. WPI has been picked up by mritter and Kel and a new major update has been released just recently. I guess because the software is not tied to XP but works with Vista and 7 as well. That's of course great! Some of the addons for slipstreaming applications with nLite/RyanVM are outdated. There is a list of addons at wincert. I personally prefer the WPI way anyway for non-system related apps - makes the installation more flexible. The WPI addons sub-forum seems mostly outdated as well, but I guess everybody is doing his/her own config since it is not too hard. I am still in the research phase when it comes to WPI. Another topic that puzzles me is themes. There are various (slipstreaming) addons at wincert, nLite can obviously slipstream any locally installed themes as well, and there is XPtsp which has a fancy website but I see only 6ish themes for it. And of course some of those are standard themes, some include boot screen and start screen mods, and some even patch some of the system dialogs. I'm a bit lost where to go... I also wonder whether it's worth to get into .SIF files. I appreciate any feedback, hints and advise. Did I get anything wrong? Did I miss anything (any tool)? Should I post in the Windows XP forum? Where is the bathroom? ... mistaecko
×
×
  • Create New...