I'm not very familiar with how amiupdate & appdir works yet but as i said earlier. if i run appdir:amigaamp3 from a shell amigaamp3 starts so the path must be correct i think. But i will mess with it again tonight just to show that i'm not some ignorant guy who doesn't listen to the suggestions ;)
What bothers me is that if i have snoopy running and executes an update within Amiupdate i can see how it searches for alot of applications and files but there's no entry for Amigaamp3 at all.
AmiUpdate's "supported applications" thing only looks in ENV:AppPaths (which is the old AmiUpdate specific version of ENV:AppDir). Anything that is found directly by path won't appear in there either. Basically just ignore it, it's of little use.
Yes, AmiUpdates "Supported Applications" is a legacy thing from before AppDir: even existed. It's only of use to AmigaOS 4.0 users. it will be removed in a future update.
For those having problems getting updates recognised, enable the "Verbose Log" option, do a scan, and check the log. It should show you enough information to determine why it's not doing what it is expected to.
Simon
Comments made in any post are personal opinion, and are in no-way representative of any commercial entity unless specifically stated as such. ---- http://codebench.co.uk
Rigo wrote: Yes, AmiUpdates "Supported Applications" is a legacy thing from before AppDir: even existed. It's only of use to AmigaOS 4.0 users. it will be removed in a future update.
For those having problems getting updates recognised, enable the "Verbose Log" option, do a scan, and check the log. It should show you enough information to determine why it's not doing what it is expected to.
Simon
Thanks Rigo! That was a good tip. I get this message:
22:58:08 Now checking: AmigaAMP3... 22:58:08 This update is not applicable to the host hardware.
Something must have gone wrong there. I have a Pegasos2 and i'm sure it's supported.
All platforms are enabled now, so it should be fixed.
It's always worth a mail to the application author after checking the log, it might be quicker...
Simon
Comments made in any post are personal opinion, and are in no-way representative of any commercial entity unless specifically stated as such. ---- http://codebench.co.uk
I read in changelog to 3.8, that it now possible to choice just directory instead of single files, and amigaamp will scan whole directory and add files from to playlist. I tried that and seems it didn't works. I.e. i just press "open", go to work:, choice directory "music", and press "OK" in asl requester => nothing loads in playlist.
kas1e wrote: I read in changelog to 3.8, that it now possible to choice just directory instead of single files, and amigaamp will scan whole directory and add files from to playlist. I tried that and seems it didn't works. I.e. i just press "open", go to work:, choice directory "music", and press "OK" in asl requester => nothing loads in playlist.
The new "load entire directory" feature was completely borked (caused crashes, even). Should be fixed in 3.9.
Everytime i try to iconify the prefs window i will loose the icon everywhere on my Workbench
Pls can you fix it for the next release ?
All right, what exactly seems to be the problem? On my system, iconifying the Prefs editor will put the icon just below ramdisk, where icons are normally placed after iconificaton. Is the behaviour different on your machine?
nbache wrote: Yep, it does that here too. I think it is using the snapshotted position of the program icon in the original drawer.
I tried snapshotting both the AmigaAMP-Prefs and the AmigaAMP icon, on various places on the Workbench screen. When iconifying the Prefs, the icon always appears below the RAM Disk, not in the snapshotted position. Just how can I reproduce the problem you're having??? I'm quite lost here.
I don't actually regard it as a problem as such, but what I observe is that the icon of the AmigaAMP-Prefs program is snapped inside my AmigaAMP3 window at 202,11 (this can be seen in the information window), and when I run the prefs program from its icon and iconify it, the AppIcon is placed at exactly that position on WB. And this is what I confirmed.
Maybe you have something else at or near those coordinates which prevents the AppIcon from being placed there? In such a case WB will choose another place for it.