Is there a way to suppress the Log window?

Ive been creating my first set of songs/Set list, and each time I choose a different Rackspace I get the Log window with the message in the screen shot pop up.
After investigating this I found that it was a Global script that i have running to start each RS from the first variation when GP is first run. I can see how this is interfering with other things.
It was just a warning and didn’t stop me getting the Songs sorted, it was just annoying.

Ive deleted the script and now I dont get the window pop up, but was wondering If I can have the script running and just suppress the window? I can move it out of the way but that’s not an elegant fix.

You can incorporate the CloseLogWindow () function into your Global script, though the timing of the callback you will have to figure out as you want it to occur after any error messaging, and not before.
https://gigperformer.com/docs_5_0/SystemFunctionList.html#CloseLogWindow

Those popups are intentional and in such cases they will always popup – that’s by design.

Did you read the warning? It’s telling you that you can’t change a variation while you’re in setlist view. You shouldn’t be trying to do that — hence the legitimate warning.

So either remove the code that’s trying to change the variation or put in a test to make sure that you are not in setlist view when you try to change a variation

1 Like

First off, i had no idea what it meant. Yes of course i read it, about 20 times.
Had it been a bit more specific i wouldn’t have had to ask.
As far as i know once GP has opened it had reset all the Rackspaces so what was it doing still working? I wasn’t aware it was always working and i certainly won’t trying to change them manually.

I have removed it and it’s gone so it all fine. I was just asking if there is like a ‘don’t show again’ type of setting that other programs sometimes have.

Well, then, asking what it meant would have been the next step :slight_smile: From where did you get that script? I guess you didn’t write it yourself.

The “don’t show again” is not really for warnings. It’s to let you know that a particular behavior will occur and once you KNOW that behavior, you don’t need to keep seeing the information.

But scripting is completely different. You should never have code in a script that won’t work under some circumstances -that’s potentially a bug.

So the purpose of the log window popping up automatically is to get you to fix the problem.

1 Like

Well it was from the Admin of the FB page (who also manages this community i believe), so i had no doubt it was legit. I wanted it to do a certain thing and the script did that.
As i said, this was my first time using songs and i wasnt doing anything wrong, and wasnt aware the script was as the message really isnt as clear as it could be unless you know GP and whats going on under the hood.
I
‘Changing variations’? Well to me that clicking on different variations, and thats pretty much what you have to do to create a song, so how was i to know what else was going on?
I figured it out myself so i did learn one thing today, two if you count ‘don’t expect an easy ride’ lol.

Im sure in time ill get used to all this, and i really didnt want to get in to scripts at this stage, but ive only been using GP for a few weeks and have to get a full set list ready for next friday, im learning one thing at a time as i go and trying to only learn what i need.

There are multiple admins of both the FB page and for this community.

I would encourage you though to ask your questions here rather than in FB - many more users will see them.

You were not - but you didn’t make it clear that you were not familiar with scripting so I assumed you were :slight_smile:

GP Script is a very powerful tool to manipulate Gig Performer in ways that are not available via the normal user interface but it does require some learning.

You got this script on Facebook?
Can you please post the content of that script and tell us why have you used it, for what purpose?

As I said, I got the script from the Admin of the GP FB page, it wasnt just a random script.
I had asked if it was possible to have GP always start with the first variation of each Rackspace when I first open GP. I sometimes forget to select the first one when I save GP. I was a minor irritation and i wondered if there was a setting for this. It works perfectly but I had no idea it would cause issues somewhere else.
Still very new to GP and in fact this is the only scrips ive ever used.
I’ll post the script later when I get home.

Yeah, it was probably me – and I just wrote something really quickly since (if I remember correctly) you wanted to open the first variation of each rackspace.

Had I known you were also going to use this in SetList mode, I would have added the extra test to make it “immune” to setlist mode.

GP Script lets you do lots of things but, as with all programming situations, it’s very “literal” and you have to handle all the possibilities :slight_smile:

1 Like

Ah right. I thought it might have been but don’t have access to FB at the moment so couldn’t check.
Yeah, that script worked exactly as I wanted it to, and at the time I wasnt going to be using Setlists. In fact I think I mentioned that I knew Setlists would do this but I wasnt using them.
now ive progressed to using Setlists I don’t really need the script, but it was a big help while I did.
I used to code in MS DOS occasionaly so I know how precise you have to be with this sort of thing. A whole other level of Rabit hole to go down lol,

Hi David.

Any chance you could re write the script with the change so it doesn’t affect Set list mode please.
I know it’s been a while but I could do with that script again, but with the modification. Still haven’t go around to working with scripts yet.
No problem if you dont have time etc.

This is the post im referring to
'Yeah, it was probably me – and I just wrote something really quickly since (if I remember correctly) you wanted to open the first variation of each rackspace.

Had I known you were also going to use this in SetList mode, I would have added the extra test to make it “immune” to setlist mode.

GP Script lets you do lots of things but, as with all programming situations, it’s very “literal” and you have to handle all the possibilities :slight_smile:"

Sorry, I’d have to see the script….not sure what it does and I’m not really in a position to write and test new scripts from scratch these days…busy writing code for GP itself

1 Like

You got this script on Facebook?
Can you please post the content of that script and tell us why have you used it, for what purpose?

Oh, I think someone already asked this before… :wink:

No problem. I’ll see if I can find it over the weekend.

Yeah, it was via the GP Facebook group. Before I came on here IIR.

This is what I got. Ive just copied it from the FB post.

// Called when you switch rackspaces
On Rackspace(oldRackspaceIndex : integer, newRackspaceIndex : integer)
SetVariation(0) // Switch to the first variation
End

It worked fine until I started to use set lists. Then I would get an error window pop up telling me something was wrong. I could dismiss it but it becomes quite distracting.

Oh, I see.

Well, two options:

  1. — just remove that callback from the global rackspace or

  2. — change it to this

On Rackspace(oldRackspaceIndex : integer, newRackspaceIndex : integer)
   if not InSetlistMode()
      then  SetVariation(0) // Switch to the first variation
   end     
End

In both cases, recompile after you make the change

2 Likes

wow, thanks very much.
Honestly, I have no idea about the first option, but I can figure out the second one. This (your previous script) is the only one ive ever used. Still got a lot to learn.

Thanks again.

The first option is to just delete the script completely — if you’re not using rackspace mode, then you don’t need it at all.

1 Like