- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Force kill of screen from stack

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Force kill of screen from stack
Void Close()
Close the screen and delete the associated object. Useful for avoiding screen flicker when the display order of your screens does not resemble a stack.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Force kill of screen from stack
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Force kill of screen from stack
Is there any way to manage this operation today?
I can not remove my roScreen from the stack, the suggest method does not work this days (Close() is no longer part of roScreen object I guess)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Force kill of screen from stack
@tBibi, why do you think this no longer works? Close() is certainly still there. What are you trying to do? You shouldn't have multiple roSGScreens in a stack. Use scenes instead.
Caveat: I am no expert on scene graph as I absolutely hate it.
Help others find this answer and click "Accept as Solution."
If you appreciate my answer, maybe give me a Kudo.
I am not a Roku employee.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Force kill of screen from stack
I am using the 2D api roScreen and not the sg one. The function does not exists on that component as I understand.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Force kill of screen from stack
I think setting the screen to invalid effectively closes and removes it from the stack. I have never had a reason to use more than one roScreen. I have had to rebuild the roScreen after displaying an ad though.