Graphics

 View Only
  • 1.  Importing/Exporting E-GPIs?

    Posted 02-05-2019 13:49
    Hello,

    Going to try my best to post questions here for the benefit of others.

    I've made a football scoreclock utility with Dashboard, and have a project with various different graphics for the different league graphics packages. Scene is filled via a Datalinq from Dashboard, and the scenes are controlled via e-gpis as suggested by Ross.

    Now I want to make these scenes work in the "master" graphics project instead of the clock-only version.

    Problem is it seems these e-gpi scripts, and the "master methods" associated with them live in the project, and there doesn't seem to be a way to import/export them.

    Am I missing something, or am I writing a feature request ? :)

    BTW I've tried the Project Group thing, but the e-gpis only fire if the clock project is "active" and that's too tight a restriction for the use case.

    -Adam


  • 2.  RE: Importing/Exporting E-GPIs?

    Posted 02-05-2019 14:26
    Hi Adam,

    The GPI scripts should execute whether the project is active or not.. Can you give a specific example of one that fails to run when not active? The most common culprit is using Engine.GetxxxByName etc, and this fetches the object from the active project. In most cases there are equivalent methods in the xpProject api, so the call should be something like Project.GetxxxByName instead.

    There is a round-a-bout way to move keyboard/GPI events to another project, but it is not as simple as an export/import. You can drag keyboard events from the "Project Shortcuts" section of the tree into the "Global Shortcuts" (but you first need to make sure you aren't set to the "default" keyboard map). Then you can activate the other project and drag them from the "Global" to the "Project" section. DO NOT SAVE THE FIRST PROJECT NOW (or it will save it without those shortcuts now). Alternatively, if you want these shared amongst many projects maybe leaving them in the "Global" section is best. These get saved to a .KDB file that can be moved to other machines as required, they no longer live inside the XPF file anymore.




    #XPression