WHDLoadMenu

[Radertified]

Hopefully there's not too many icons that have lines like that.

Or if there's a fix for WHDLoadMenu... even better!

But it's no big deal if it's just one or two slaves like that.

[yelworC]

As far as I remember this garbage in the tooltypes is the icon image data of the Newicon system. This is normally hidden, when icon library is capable of displaying these icons either by the newicons patch or simply a more recent icon.library.

[DamienD]

Originally Posted by yelworC

As far as I remember this garbage in the tooltypes is the icon image data of the Newicon system. This is normally hidden, when icon library is capable of displaying these icons either by the newicons patch or simply a more recent icon.library.

As far as I know, agreed

[Vesuri]

Originally Posted by Jope

Could be that the »»»» Icon by Michael-T. «««« line might be the culprit here.

I can confirm this is exactly what's causing the issue - not the NewIcon lines.

WHDLoadMenu currently uses all tooltypes as WHDLoad arguments as is except ones starting with one of the following:

• ;
• (
• *
• IM1=
• IM2=

Apparently » should be added to the list. This will be added in an upcoming release. For now, please comment out that tooltype by adding parentheses around it or by deleting the line altogether. Thanks for the bug report!

[Radertified]

Fantastic! Thanks for the upcoming fix, Vesuri!

[emuola]

Originally Posted by Vesuri

I can confirm this is exactly what's causing the issue - not the NewIcon lines.

WHDLoadMenu currently uses all tooltypes as WHDLoad arguments as is except ones starting with one of the following:

• ;
• (
• *
• IM1=
• IM2=

Apparently » should be added to the list. This will be added in an upcoming release. For now, please comment out that tooltype by adding parentheses around it or by deleting the line altogether. Thanks for the bug report!

Awesome Vesuri! Thank you!

[Vesuri]

Originally Posted by Radertified

Is it possible to have WHDLoadMenu scan multiple paths?

WHDLoadMenu 1.1, now available from AmiNet, adds the possibility to scan multiple paths. The installer script does not ask for multiple directories so you will need to modify the RunWHDLoadMenu script manually to add more paths. Just add the extra paths right after the one you entered during installation on the WHDLoadMenuScanner line.

Originally Posted by emuola

Stumbled across on weird issue with Tiny Bobble.

WHDLoadMenu 1.1 now ignores » characters in icon tooltypes, which will fix the issue with Tiny Bobble.

[Radertified]

Thanks for the fixes, Vesuri!

[Vesuri]

WHDLoadMenu 1.2 is now available and it significantly improves the startup time (almost tenfold) when there are lots of WHDLoad slaves to be displayed.

[emuola]

Originally Posted by Vesuri

WHDLoadMenu 1.2 is now available and it significantly improves the startup time (almost tenfold) when there are lots of WHDLoad slaves to be displayed.

Works super fast Thank you Vesuri

[yelworC]

Wow! This is so incredible much faster than before! Great work!

A nice feature would be the ability to somehow open the readme for the selected slave. it sometimes contains useful Info about possible cheats and stuff like that.

[lesta_smsc]

Originally Posted by Vesuri

It can be run from a shell, preferably using the provided runner script. When the user selects the applcation to be started from the menu, the menu generates a script which will run the selected application using WHDLoad. After this the menu itself exits and the runner script runs the generated script. This way the menu itself is not in memory at all when WHDLoad is started, leaving the maximum amount of contiguous memory available for WHDLoad.

Interesting. I presume memory flush is done by WHDLoad during start up as well. Can this be modified to say run in reduced bitplanes? This way the games needing the extra bytes will work as the menu itself does not need and more than 2 colours yet this will offer maximum RAM availability for WHDLoad. I've successfully booted many games that needed additional RAM by running from shell in reduced bitplane eg via add21k.

[Vesuri]

Originally Posted by lesta_smsc

Can this be modified to say run in reduced bitplanes? This way the games needing the extra bytes will work as the menu itself does not need and more than 2 colours yet this will offer maximum RAM availability for WHDLoad. I've successfully booted many games that needed additional RAM by running from shell in reduced bitplane eg via add21k.

WHDLoadMenu comes with two user interfaces: a standard Intuition one and a custom one. The Intuition one should work on a single bitplane screen (haven't tested it though). The custom user interface, on the other hand, does not use an Intuition screen at all. When started from the beginning of the startup-sequence, no Workbench screen is opened either. Since WHDLoadMenu is not in memory at all when WHDLoad itself is started, the custom user interface can use all the system memory and all the memory will still be available for WHDLoad. Because of these reasons I'd say no modifications are necessary.