MAKI Cheats

[garetjax]

I am thinking this only needs to be several animatedlayers in the player xml; one for each state. Then it should be a matter of just enabling them in some way (like using the width/height = 0 when not in use and when x (button) is clicked set their width/height.

This is a hack; but one that should be relatively easily used.

Sample RunningDisplay.m

code:


Global AnimatedLayer1 layerStaticCassettes;

Global AnimatedLayer2 layerRunningCassettes;

Global AnimatedLayer3 layerFastRunningCassettes;

Global AnimatedLayer4 layerRewindRunningCassettes;

Global AnimatedLayer5 layerPausingCassettes;



initBehaviors() {

 AnimatedLayer1.hide();

 AnimatedLayer2.hide();

 AnimatedLayer3.hide();

 AnimatedLayer4.hide();

 AnimatedLayer5.hide();

}



System.onPlay() {

 AnimatedLayer1.hide();

 AnimatedLayer2.show()

 AnimatedLayer3.hide();

 AnimatedLayer4.hide();

 AnimatedLayer5.hide();

}



System.onStop() {

 AnimatedLayer1.show();

 AnimatedLayer2.hide()

 AnimatedLayer3.hide();

 AnimatedLayer4.hide();

 AnimatedLayer5.hide();

}

System.onPause() {

 AnimatedLayer1.hide();

 AnimatedLayer2.hide()

 AnimatedLayer3.hide();

 AnimatedLayer4.hide();

 AnimatedLayer5.show();

}

System.onResume(){

 AnimatedLayer1.hide();

 AnimatedLayer2.Show()

 AnimatedLayer3.hide();

 AnimatedLayer4.hide();

 AnimatedLayer5.hide();

}



System.onNext() {

 AnimatedLayer1.hide();

 AnimatedLayer2.hide()

 AnimatedLayer3.Show();

 AnimatedLayer4.hide();

 AnimatedLayer5.hide();

}

System.onPrev() {

 AnimatedLayer1.hide();

 AnimatedLayer2.hide()

 AnimatedLayer3.hide();

 AnimatedLayer4.show();

 AnimatedLayer5.hide();

}

Note: This is pseudo code for a maki script to handle animated layer swapping based on user clicks.

[scottiescotsman]

I like the theory as same was in flash I was doing a project.
question 1
wouldn't all layers be running constant even though invisible?
question 2
or would you save the position of the active layer on button click so that the next visible layer would start as the same position ?

thanks for your help guys
Steven

ps. if we or you lol figure this out it be so cool for all different animations in winamp skinning

[garetjax]

The hide method disables the acrive layer. Technically it is still running I suppose, but as it is an png is should be very limited...And of course you could just disable the frame entirely instead of hiding/showing. And yes ro question 2, the ordinal position are.expected to be in the same position...though it could be u used in any situation.

[Victhor]

When I get home I'll compile it and test it, it's a handy script to have.. It's probably missing a few lines but it should be straight forward (like EVERYTHING in Winamp skinning lol)

[scottiescotsman]

05:03 am here waiting on the test results and designing the eq

[Victhor]

Oops, I totally forgot about it, sorry, maybe tomorrow, now I'm off to sleep!

[garetjax]

Funny, technically speaking I have yet to create a modern winamp skin.

[scottiescotsman]

well get to it

[scottiescotsman]

Cant get my maki script to compile windows 10 pro grr

[Plague]

If you want to spin the layers via scripting, I did that on an old Stargate skin years ago.
The gate itself is the seeker, and spins clockwise during playback.
There is also a "simulator" mode, where the gate can be dialed, like in the show, and the gate will spin both directions and lock chevrons, just like in the show.

Feel free to dig around the code and use what you want:
Stargate Winamp - SG1 Edition

The scripts you might be interested in are:
scripts\lib\rotationlayer.m
scripts\gate-playermode.m
and maybe:
scripts\gate-simmode.m

[scottiescotsman]

biG tA!

Thanks m8 will have a look as I know zero about maki

and most other things lol

quick question...

how do I get a toggle button to hide then unhide a layer?

Thanks
Steven

[Plague]

It was ages since I last played with maki, but basically if you want to specifically use a tooglebutton (so that it stays pressed when the layer is in one state, and then stays unpressed when the layer is in another state), then I'd suggest using cfgattribs for that.

For example, in dhd-playermode.xml, you find this line, that will toggle the iris on the gate:

code:


<togglebutton id="Iris" x="244" y="133" image="dhd.Iris" downImage="dhd.Iris-on" activeImage="dhd.Iris-on" tooltip="Toggle Iris" cfgattrib="{258968BA-8E47-453c-A008-4433A6EB298E};Iris"/>

The cfgattrib is the interesting part, the GUID you see there {258968BA-8E47-453c-A008-4433A6EB298E} is for a hidden config page in Winamp.
After the GUID, you specify the variable you want to use (Iris).

Then, in attribs.m and gate-playermode.m, you will find the needed script code to handle it.

Basically, you need to add the attrib in maki and use it to toggle the layer you want to show/hide.
For example:

code:


#include <lib/std.mi>

#include <lib/config.mi>

#define HIDDEN_PAGE "{258968BA-8E47-453c-A008-4433A6EB298E}"

Global ConfigAttribute myattr_toggleIris;

Global Layer iris;

System.onScriptLoaded() {

  ConfigItem hidden_page = Config.newItem(getSkinName() + " Hidden", HIDDEN_PAGE);

  myattr_toggleIris = hidden_page.newAttribute("Iris", "0");

  Group sgroup = getScriptGroup();

  iris = sgroup.findObject("iris");

  myattr_toggleIris.onDataChanged();

}

myattr_toggleIris.onDataChanged() {

  if (getData() == "1")

    iris.show();

  else

    iris.hide();

}

The reason for using cfgattribs is that the layer and buttonstate will always be synced.

[scottiescotsman]

Thanks

Cheers m8 saw this last night but was to sleepy to comprehend what the code was doing

Now that I am awake lol I giving it a go!

Thanks a lot
Steven

p.s Is there a maki book that I could get to learn it ?

also I read a few of the posts on forum about where to store/learn/teach the maki scripts to the masses. I have a web domain that I have had for ages and have struggled to find a useful use for it but would gladly hand to someone to do as they please for the purpose of store/learn/teach the maki script

[Plague]

No there is no maki book as far as I know.
The best source for learning maki was the so called "Canada" documents, but those are offline since a very long time.

There is a Wiki for Modern Skins that you can use for reference:
http://wiki.shoutcast.com/wiki/Creating_Modern_Skins

Otherwise, I'd just suggest digging into the included .mi files in Winamp, for example std.mi and config.mi.
They have good commenting on most of the functions to help you understand how things work.

Another tip is to start digging through a simple skins sources, for example the Winamp3 base skin or the Wasabi.player base skin (links in my signature).

My D-Reliction skin (link in my sig) could also be a good source for doing a little bit more advanced stuff, without it getting too complicated to understand.

All my maki sources are included, and they should be fairly easy to understand.

The Bento and Winamp Modern skins are in my opinion built in a way that is a bit too complicated if you want to learn basic maki.

Also, dig through this forum thread, from the beginning, as there are tons of useful small scripts and tips right from the start.

[scottiescotsman]

I give up I cant complete my skin as I don't have the knowledge or xpertise so I will leave it there

ta