Nothing personal but using the image of a child as an Avatar doesn't exactly instill confidence in your programming skills. Clicking on the WEB site link in your profile and seeing a picture of 4 bare asses doesn't say much for your maturity either. I can only imagine what an Internet savvy employer will think when he researches you on the Internet. Think about your future and project a positive image.
Amiga X1000 with 2GB memory & OS 4.1FE + Radeon HD 5450
@xenic Well, that child is me at age of 5? Don't remember. No ofense, about my website, its loong ago abandoned and yes one of those asses is mine My coding skills? Quite low, just see Poff (os4depot) and Mixer V.134, cooming soon V1.35 (now playing with application.library/docky to try to add a Mixer docky).
@Elwood Ok, changed from NOAPPMENU switch to APPMENU=YES/NO toggle
@Raziel Not 100% sure, but the X1000 hdaudio can not (as is Mixer now) be implemented
BTW do someone knows how to update the AmiUpdate database entry of Mixer? It still says V1.32 and would like to change to V1.34 or (upcoming) V1.35 that has Autoinstall script.
TIA
Edited by jabirulo on 2013/8/19 20:52:00 Edited by jabirulo on 2013/8/19 20:55:23 Edited by jabirulo on 2013/8/19 20:58:53 Edited by jabirulo on 2013/8/19 20:59:28
Updated via amiupdate, all going fine, through when i press on "info" button, it only shows that "update for your program", but no change log. Will be cool to have it for future versions.
Also as i see now there is Skins directory (all is ok), but inside 2 directories: Default and Images. Calling one of skins as "Default" is right, but calling another one as "Images" is wrong for sure. Also as i see another skin do not works. I.e. if i choice "default" one, its default, and if i choice "images", its still default. While there was 2 skins : one was in "images" another was in "images_old", so imho should be just now "default" and "old_look" or so where put all images from old "images_old" directory.
But alas I don't know what the user did with the (old) Images drawer (changed contents or...) what I did is just move inside Skins drawer. (Autoninstall script will be improved for "next?" version).
You can look on your "new" Mixer drawer so you can move, if you have, previous skins/images to Skins.
But alas I don't know what the user did with the (old) Images drawer (changed contents or...) what I did is just move inside Skins drawer. (Autoninstall script will be improved for "next?" version)
It was the same as with Skins, just name was "Images", and there was 2 skins "Images" is one of them, "Images_old" is another one. User just choice in image tooltype "Images" and have one skin. If he choice "Images_old" then he have another skin. For now you just remove one of skins :)
So, to make all logic, you just need to put all Skins we have to the Skins directory, and give them some normal names (not just "Images_old", but something like "Old_Look").
I.e. now you just remove "Images_old" directory, while it was old-looking skin. I.e. you should put it back to skins directory, just give it a proper name like "old_look" or whatever. Default skin can stays as default of course.
@jabirulo Just add them like Skins/old_look or so, no need to create again "Images" directory or even call old skin as "images_old" (can be just confusing , as it all now called skins, etc).
Since 1.35 (final) i can't be able to add Mixer to the tools menu anymore, it sems that the latest modification in tooltype you added doesn't work correctly
APPMENU=NO --> shoud turn off the tools menu entry, and it do exactly that
APPMENU=YES --> same result an APPMENU=NO while once you select the "hide" item from menu it should put Mixer into the tool menu as before
Uuuh, can you check you don't have any other APPMENU tooltype enty? Tried here APPMENU=YES and no problems, I get 'Mixer' in Workbench/Tools menu BTW seems is (sort of) broken from Shell/CLI, will fix it ASAP.