Your best bet is to wait until i reclass and package it to that you dont have any issues.Once im happy with it I will release it in the form of a plugin with a simple toggle on/off for skinned elements.
Adding it manually is ok, depending on what your trying to add. there are alot of material components that wont suit just adding markup or a html element.
Thanks @jarrad. Can’t wait till you release it then
Got it all working last night, now I need to find a smart way to trigger the click and not end up in a loop with the mouseover event.
So there is the document ready function, but is there also a way to do that with a repeating group?
if I run the remove and add classes conditionally in one workflow, the repeating group is too slow to load so it cannot add the class. I can add a pauze, but some of my users have an unreliable connection so that is not safe.
If I can target the loading event of the repeating group in the custom code block, I can have it run when the RG is loaded and also don’t have to worry about the classes being not added.
I looked at the jquery events I could utilise but I guess I need to brush up on my jquery knowledge.
Do you already regret opening this topic 
no, i just regret making the tools free… lol. Come on @vincent56 i would have thought you would see the answer to this one… why did i make the slide menu bounce around like an idiot and react to mouse events? so look at it like this, we clicked a button using that code… now look at the code itself…
$(’#bg’).mouseover(function(){
$(’#trigger1’).click();
});
so the click happens on mouse over, eg… open/close/open/close. what told the code block to run?
try this…
$(’#bg’).mouseover(function(){
< — distract the mouse.
});
wait for page load,
$(’#trigger1’).click(); 
< ---- With this… he will only run once. trust me.
I gladly compensate you for your trouble 
I’d rather buy your plugins though 
So what you are saying is to break up the code and have the last part run on page load. I’ll try some things, but so far the page loads before the data in the RG is visible so things fire before there is data in the RG.
but if the button was referenced to the rg’s data, and conditioned to not be visible then your code blocks only when could say on once page has loaded and only when that button is visible, you more than welcome though mate… glad you got some use out of the demo…
Is there an issue with the slide menu? When I look at the demo the menu seems to be sliding in and out pretty randomly. When I use this on a popup it also still ‘remembers’ the full width and height of the original popup window.
You can then not click that area (that will look as if there is nothing there since the popup was resized) to close the window.
