Maintaining fullscreen/windowed between executables

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.

    I have a game that has several executables, each of which open new executables and self-terminate in order to keep memory usage within allowable parameters.

    I'm using an .INI file to store some data between these executables. I was thinking to use a variable within the INI to let the newly opened executable know whether it should be windowed or fullscreen, thus keeping the same status as the prior executable.

    However, while the Global Events menu allows you to attach an event to "Fullscreen" (Has an option been selected? -> Application Menu -> Options -> Full Screen (Alt-Enter)), it does not appear to have a similar option for "Windowed", nor does it allow you to "negate" that "Has Fullscreen been selected" event.

    Does anyone know a work-around?

    I can, but then if someone makes it fullscreen and then returns it to windowed, there's no (apparent?) option to tell the program that state... So the variable changed in the .ini file would remain the same, and the next executable would be fullscreen.

    What if you use "Is a menu option checked?" instead of "Has an option been selected?" and then negate that? You can toss in a "Only one action when action loops" too so it doesn't execute more than once.

    That memory issue sounds odd though. Perhaps there is an alternate solution to having multiple .exe files?

    Please login to see this link. Please login to see this link.
    Freelance Dev | Currently Working on Jarvis | Please login to see this link.

Participate now!

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

Register Yourself Login