We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.

Monokultur-Studio

Forum Replies Created

Viewing 3 posts - 16 through 18 (of 18 total)
  • Author
    Posts
  • Hi Mikhail,

    yes Puzzle is the way! ;-) But I dont know how to change the states permanently in puzzles…

    I also tried to configure the “new state” manually in puzzles.
    Example:

    the button is just a black box. But I want this box to have a box shadow after being pressed. The divs’s ID is: button_1
    So I use the set style puzzle set to box-shadow to 0 7px 13px 5px #000; for elem button_1.

    But nothing changes. What am I doing wrong?
    If I set the style display to none for elem button_1 the button disappears. So the ID is correct…

    Attachments:
    You must be logged in to view attached files.

    Hey eeey,
    yes the states work when the project is exported, but there is no way that the buttons stay in one of the states.

    In my app I have 2 buttons. Whith those buttons I can change between two 3D-Models. It would be nice if the last clicked button would stay in its changed state after being clicked to have an optical feedback inside the ui of which 3D model is the active one. And if I click the other button and the models change than this button stays in the clicked state and the first button switches back to the normal „not clicked“ state.

    Is something like this possible when working with webflow without creating a new css class or manually changing multiple css rules with puzzles?

    Ok thanks for your answere! :good:

    Where do I implement those custom features? In the “my_awesome_app.js” in the function runCode(app) {} section? Cause I tried this:

    function runCode(app) {
    controls = new v3d.OrbitControls(camera, renderer.domElement);
        //controls = new THREE.OrbitControls(camera, renderer.domElement);
                controls.enableDamping = true;
                controls.dampingFactor = 2.0;
    }

    But this didn’t work. Is it because it interferes with the blender camera set to “orbit mode” or is there another place where i have to implement stuff like this?

Viewing 3 posts - 16 through 18 (of 18 total)