Unable to edit embedded code

Welcome to our brand new Clickteam Community Hub! We hope you will enjoy using the new features, which we will be further expanding in the coming months.

A few features including Passport are unavailable initially whilst we monitor stability of the new platform, we hope to bring these online very soon. Small issues will crop up following the import from our old system, including some message formatting, translation accuracy and other things.

Thank you for your patience whilst we've worked on this and we look forward to more exciting community developments soon!

Clickteam.

    Please login to see this picture.

    Issue:
    The embedded code's window does not appear, disabling me from reaching my own code. Code still runs properly, though.

    How it happened:
    I wanted to share the same xLua object through 3 frames. I copied the xLua object I had with written code to all 3 frames, and it worked like a charm.
    However I quickly discovered that an edit in one object didn't carry over to the remaining in the different frames. I tracked down the xLua object that contained the code which was being used (turns out to be the last created of the objects).
    Then I emptied the other objects so I wouldn't accidentally spend hours writing in the wrong object.

    After restarting MMF2, the window now appears as seen in the screenshot above. I'm unable to reach the code.

    Help needed!
    Mecha the Slag

    The first thing i would try is replacing the object with another Xlua. Add another Xlua to the frame and in the event editor right click where you see the icon at the top and then select "Replace by another object" and then select the other Xlua.

    If that doesn't fix it make sure to not overwrite though. Maybe also downloading the object again and replacing the main extensions, i doubt that would be it though.

    There is also the .001 etc backups which you can rename back to mfa if you have them but again i am not sure if that would help but worth a try i guess.

    If you are lucky the replace with another might work, if not then i guess only Retriever2 can help.

    1) That... wouldn't work. My scripts would still be stuck, irretrievably, inside the original xLua object.

    2) Yeah I have the newest version already D:

    3) The bug persists in all of my 10 latest backups - as I mentioned, it didn't occur until I restarted.

    The only way out of this mess as far as I can see, is getting RII to add some kind of 'export' button so that I can export all my scripts... but I have no idea if he's even active here anymore.

    Wait - don't tell me this is the first time you encounter this. I've had this problem for months. It *always* happens - it's so annoying that I kind of lost any motivation to use the extension's inbuilt script editor at all :(

    Please login to see this link.

    Sorry that was not much help :(

    This was posted recently (Possible Java XLua) -

    Please login to see this link.

    So i think Retriever2 is still active here, hopefully you will be able to sort this.

    Woah, if some of you have been having this problem for months why is this the first time I've ever heard of it? D:

    I may not be actively developing new extensions, but I still check these forums almost every day explicitly so I can continue to support XLua. Also you of all people Mecha should know how to get hold of me if you need to.

    Interesting bug, could you please send me your MFA file (or try to reproduce the problem following your own steps as described?) XLua objects across frames (especially copied) is an area that hasn't been probed deeply so clearly it needs a little work still.

    I promise everyone here that the day I am no longer willing to support XLua, I will announce that fact and offer the source code to the community to continue maintaining it. Even if I get hit by a bus tomorrow, Clickteam still holds a copy of the source.

    Really? Wow, I was pretty sure that I reported this bug on Gwerdy Chat quite a while ago, and you thought you had fixed it, but you really didn't - must be mixing something up then. Anyway, good luck fixing this one, would be pretty awesome!

    Please login to see this link.

    Hi Retriever,

    Sorry to bump in this, but i get the same issue as mentioned here, you may see this way,

    Open the "OpenGl" example and you get the 1 in the editor.

    close the example and

    Open the "socket" example and choose to edit and you will that the edit control (or scintilla) in not available.

    Also i wonder if you build any of the lua library concerning sqlite (luasqlite-0.4.1 or lsqlite3.7 or luasql2.1.1)

    Regards,

    Regards,


    Fernando Vivolo

    ... new things are coming ...

    I apologize for the delay -- I haven't forgotten about this. I've just been very busy with University work and job hunting (just accepted an offer today, and XLua may have helped me secure the offer).

    Again, sorry for the delay. Finishing grad school can be hectic.

    I believe I have fixed this problem. The Scintilla editor only went missing if the XLua module was unloaded (e.g. all XLua-containing projects are closed), and then reloaded (when a new XLua-containing project is opened). If you closed MMF entirely, then everything would be okay the next time you opened it. It was a cleanup problem.

    Please login to see this link. (Version 1.5.2)

    Re-reading the original post, I actually am not sure if I've solved the original issue. I know I solved the issue that FVivolo gave me steps to reproduce the problem, but it sounds different from what Mecha reported.

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!

Register Yourself Login