How to Delete?

[broconne]

I am having trouble issuing a delete from my STVI plugin.

I perform a AddStaticContext("Airing",AiringObject) - in which the airing object is my object and then I reference OPUS4-91972.

This part seems to work as expected. However, if I say no to the delete and then later perform another AddStaticContext with a different airing object, I am still prompted to delete the first airing.

Anyone run into this before?

[GKusnick]

AddStaticContext is meant for passing parameters from one menu to another, and seems like overkill for setting up a variable for a shared piece of code that doesn't involve a menu transition. For your purpose, an attribute variable should be adequate.

That said, I don't see any obvious reason why AddStaticContext shouldn't work. So perhaps there's a bug in your code somewhere such that Airing doesn't contain what you think it does.

In general, it's much easier for us to diagnose problems of this sort if you show us screenshots of the actual code you're trying to debug, rather than just describing in general terms what you're intending to do. The bugs usually turn out to be in the places where the code doesn't accurately reflect your intention.

If you don't want to tip your hand about what you're working on, construct a generic dummy example that exhibits the bug and show us that instead.

[PLUCKYHD]

I actually think you are right Greg I don't think a static context can be changed again assigned unless a MENU transition occurs.

But back to the question agree with Greg what you are referencing is just a popup so definately just set an attribute value before linking to the popup. If this is on the a table just set the attribute vale under the item widget for all cells then you don't have to do it over and over again for multiple links.

Something like

Airing[=tablecell]

[broconne]

AddStaticContext is meant for passing parameters from one menu to another, and seems like overkill for setting up a variable for a shared piece of code that doesn't involve a menu transition. For your purpose, an attribute variable should be adequate.

Correct! I thought I needed AddStaticContext, but just a variable is fine.

That said, I don't see any obvious reason why AddStaticContext shouldn't work. So perhaps there's a bug in your code somewhere such that Airing doesn't contain what you think it does.

Hmm - not sure why AddStaticContext doesn't work - but it does not seem to - the code seems to be right because I can assign the same method call to a variable and that seems to work

In general, it's much easier for us to diagnose problems of this sort if you show us screenshots of the actual code you're trying to debug, rather than just describing in general terms what you're intending to do. The bugs usually turn out to be in the places where the code doesn't accurately reflect your intention.

Makes sense.

If you don't want to tip your hand about what you're working on, construct a generic dummy example that exhibits the bug and show us that instead.

Not afraid of tipping my hand. This is for TVB.

[broconne]

Originally Posted by PLUCKYHD

I actually think you are right Greg I don't think a static context can be changed again assigned unless army transition occurs.

But back to the question agree with Greg what you are referencing is just a popup so definately just set an attribute value before linking to the popup. If this is on the a table just set the attribute vale under the item widget for all cells then you don't have to do it over and over again for multiple links.

Something like

Airing[=tablecell]

Thanks Plucky - works great when its a var.

[Opus4]

Originally Posted by PLUCKYHD

I actually think you are right Greg I don't think a static context can be changed again assigned unless a MENU transition occurs.

I don't think that's what Greg was suggesting. I just tried it and had no problem setting a static context variable & then changing it.

However, it is true that a static context is not needed (nor desirable) for this since the value isn't being sent to a new menu.

- Andy

[tmiranda]

I'd stay away from using a global static variable called "Airing" because that variable name is used all over the default STV and it's assumed to have the correct Airing Object.

[PLUCKYHD]

Originally Posted by Opus4

I don't think that's what Greg was suggesting. I just tried it and had no problem setting a static context variable & then changing it.

However, it is true that a static context is not needed (nor desirable) for this since the value isn't being sent to a new menu.

- Andy

I trust your answer I know I have had issue with static context and not changing menu's in the past. It works fine when I changed menu items, but again it could have also been my coding

[GKusnick]

Originally Posted by tmiranda

I'd stay away from using a global static variable called "Airing" because that variable name is used all over the default STV and it's assumed to have the correct Airing Object.

This is a good point. There may be a lot of undeclared local variables called Airing. But once you've made a static context called Airing, then suddenly all those undeclared refs will bind to that instead, perhaps with unexpected results.

(Pardon the rant, but this is why proper programming languages require declarations for all variables, so that the scope is explicit and can't be hijacked.)

[PLUCKYHD]

Originally Posted by GKusnick

This is a good point. There may be a lot of undeclared local variables called Airing. But once you've made a static context called Airing, then suddenly all those undeclared refs will bind to that instead, perhaps with unexpected results.

(Pardon the rant, but this is why proper programming languages require declarations for all variables, so that the scope is explicit and can't be hijacked.)

Agreed

I stay away from global context for this very reason if an when I use them I make sure that the variable is unique to me and my work. To me it is better and easier to set a property for something global.