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.

“add HTML elem” not working anymore

Home Forums Puzzles “add HTML elem” not working anymore

Tagged: 

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #28066
    sirhc
    Customer

    Hi everybody :bye: ,
    I’ve have been working on a Vergde-file for quite some time now.
    I used to be able to use the “add HTML elem”-puzzle to make div’s and/or buttons.
    But now somehow I need to put my div’s en buttons in the actual html-file by code (like:

    ) first before I can reach them by puzzles…. :scratch:
    I don’t know how this came to be, I did update to Version: 3.1.1 but maybe it’s something else,……
    Anyone else having the same problem?
    Anyone dare to take a look?? :unsure:

    Link to online project:
    http://www.3dim.nl/SandBox/Verge3D/PC00036/Opdracht02/ (yes, I know its big)

    Link to project-files:
    http://www.3dim.nl/SandBox/Verge3D/PC00036/applications.zip

    Technical Artwork Specialist@TBL.nl

    #28107

    Hi,

    I don’t know how this came to be, I did update to Version: 3.1.1 but maybe it’s something else

    Yes, this is because of the update to 3.1.1. I recall that there were some changes to puzzles regarding the ability to add html elements and those changes required updating the default application template files.

    In your project those template files I’m talking about are my_awesome_iFrame1/Suntest.js and my_awesome_iFrame2/my_awesome_iFrame2.js. Here’s their modified versions: changed_files.zip which you can just replace the old files with.

    Normally, you could have updated the application files via the update menu in the Application Manager like this:
    update-1.png
    But(!) since they have been manually edited you obviously don’t want to lose changes you’ve made and updating in that way is not an option.
    Sorry for such an inconvenience.

    For anyone with the same problem the fix is to replace the following lines in your application’s main .js file:

    
    var initOptions = v3d.PL ? v3d.PL.execInitPuzzles().initOptions
            : { useFullscreen: true };
    

    with this:

    
    var initOptions = v3d.PL ? v3d.PL.execInitPuzzles({
            container: CONTAINER_ID }).initOptions
            : { useFullscreen: true };
    
    Attachments:
    You must be logged in to view attached files.

    Co-founder and lead developer at Soft8Soft.

    #28117
    sirhc
    Customer

    Hi Ivan,
    tnx for the quick response, U guy’s R awesome!!
    I’m gonna implement it right away!!
    I’ll let U know if it worked out!!
    again…. Tnx Guy’s

    WORKED :good:

    Technical Artwork Specialist@TBL.nl

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.