7 replies to this topic

[DesertJerry]

XP Pro w/SP3 > Started AutoPatcher > everything looked ok.

Selected left + and clicked > submenu appeared ok - with other items and/or another + to expand submenu EXCEPT when I clicked on the + beside Microsoft Windows - Updated Components all of the submenus were expanded to their maximum - which is not what is expected or should happen here.

Similar issue with Stand Alone - when AutoPatcher is started this item displays the submenu opened with everything displayed - shouild not be happening.

The window with "List of available items" should appear will all items 'closed' - the user then opens each by clicking the +.

Please standardize all to the closed position.

[ViroMan]

Your right... I will see about correcting the apms... however this will cause a few glitches on some scripts till they are tracked down and stomped on. Since modifying the directory apms invalidates several scripts at once.

[DesertJerry]

As you re-write the script and/or APMs just keep us updated and we can verify and/or comment on problems/issues. Also, it if is an easy edit or correction post an example and I can try it out here to see what happens - unless that will cause more problems than its worth.

[ViroMan]

ohh they are indeed easy fixes... all you have to do is find the offending apm and where it says "AutoExpand=True" set it to False I found about 13 of them. I have set the current official XP script strait. If you re-download it, it should be good. I can't tell since I am currently on an x64 OS so AP won't even bother to show them.

__msxml.apm is one of the files that will set AutoExpand to true.
__WMP10_noncritical.apm
__WMP11_noncritical.apm if you have it... although I don't think it is used currently
__WMP_critical.apm
__WMP_noncritical.apm
__standalone.apm
the above only seem to effect XP x86 except for the standalone.apm

All the .Net main apms as well. This reminds me... I forgot to rebuild the RTI files for the scripts I changed. XP_x86 and the two current .NET's All I had to do for the scripts is just place in the new size and MD5 values. (please don't get mad Click_Click)

Edited by ViroMan, 05 September 2012 - 07:18 AM.

[click-click]

So what's the disadvantage of having something auto expand? Actually I liked it the way it was for dotNET. One user likes it one way, others like it another way. It's a matter of preference. These are just minor details that can wait until the next time changes need to be made. At that time, if it is determined that the majority want the change then fine, change it. My problem with someone else making updates is that my setup for a given component such as dotNET no longer agrees with the rest and I have to go and compare files to see the changes and then sync them to my setup. In this case, only three apms were changed so no big deal. Now, if I had not read this thread, my dotNET setup would not have had the changes merged and the next release would not have included the changes.

Edited by click-click, 05 September 2012 - 11:00 AM.

[ViroMan]

Your right about not informing you... sorry. I changed them because I agreed with what DJ said and I probably should have waited for more input... I am a bit impulsive like that.

Edited by ViroMan, 05 September 2012 - 08:07 PM.

[DesertJerry]

Edited the APM files here - result is much better than how things had been operating.

My vote is to have AutoExpand=False the default configuration.

[Whatacrock]

I second the motion as suggested by DesertJerry.