<interface>
<field id = "test" type = "assocarray" />
</interface>
---------
while true
if m.timer.TotalSeconds() >= 5
m.timer.mark()
print "TEST 1"
print m.top.test
print "TEST 2"
m.top.test = createObject("roAssociativeArray")
print "TEST 3"
end if
end while
TEST 1
<Component: roSGNode> =
{
functionName: "start"
sleepRelease: false
syncRelease: false
waitRelease: false
control: "run"
state: "run" <----- It's running?
change: <Component: roAssociativeArray>
focusable: false
focusedChild: <Component: roInvalid>
id: ""
test: <Component: roAssociativeArray> <----- It's there
[size=85][font=Helvetica Neue, Helvetica, Arial, sans-serif]}[/font][/size]
TEST 2
timerPort = CreateObject("roMessagePort")
while true
Wait(5000, timerPort)
print "TEST 1"
print m.top.test
print "TEST 2"
m.top.test = createObject("roAssociativeArray")
print "TEST 3"
end while
Once an roScreen is created, the display stack enters "Game Mode", and other screen components cannot be used.
"gabek" wrote:
After some more testing, it seems to even be more simple than that. As long as a roScreen is created, regardless of where or by who seems to break the task. For instance, if I create a roScreen directly before starting the task makes the task not run at all.
I'm pretty sure this disclaimer has always been around for roScreen:Once an roScreen is created, the display stack enters "Game Mode", and other screen components cannot be used.
But I'm not trying to make different screens active at the same time, just trying to make network requests within a task. Is roScreen just not compatible with a ScreenGraph task at all?
"Tasks" are part of roSgScreen components, so i would not expect them to work while roScreen is in command.
We’re upgrading Roku Community to bring you a faster, more mobile-friendly experience. You may notice limited functionality or read-only access during this time. You will not be able to log in or post new comments or kudos during this time. Read more here.
Planned Downtime:
Community will be unavailable for up to 24–48 hours during the upgrade window during the week of May 12 and you may notice reduced functionality.
In the meantime, for additional assistance, visit our Support Site.
Thanks for your patience — we’re excited to share what’s next!