R4 Queue Comm module
TrikinCurt
Posts: 158
Okay,
Switching over to the R4 Comm module so I can play with browsing from the iPod. I can get that to work, but have made a mess out of the rest of my code!
In my main code I have things like
I use this to store what room the remote/touchscreen is currently controlling. On connection it fills it with the default:
The R4 Comm module is setup and the _MAIN is mapped to port 1. Should I just be able to switch references of dvTPR4FAM_MAIN to vdvR4Comm_MAIN and it will work? Because, well, it doesn't
It seems levels are confusing me, I remapped my levels to be low numbers (under 10) so that should not be an issue. Am I doing something fundamentally wrong?
Switching over to the R4 Comm module so I can play with browsing from the iPod. I can get that to work, but have made a mess out of the rest of my code!
In my main code I have things like
CREATE_LEVEL dvtpR4FAM_MAIN, 1, dvTPArrayCurrentZone[8]
I use this to store what room the remote/touchscreen is currently controlling. On connection it fills it with the default:
SEND_LEVEL dvtpR4FAM_MAIN, FamilyRoom.zoneID SEND_LEVEL dvtpR4FAM_MAIN, autopatchVolumeArray[FamilyRoom.audioSwitcherOutput]
The R4 Comm module is setup and the _MAIN is mapped to port 1. Should I just be able to switch references of dvTPR4FAM_MAIN to vdvR4Comm_MAIN and it will work? Because, well, it doesn't
It seems levels are confusing me, I remapped my levels to be low numbers (under 10) so that should not be an issue. Am I doing something fundamentally wrong?
0
Comments
Thanks Dave, that is where I ran into trouble. I have some DO_PUSH statements that seemed to be doing nothing (apparently they were!). It also seems that the CREATE_LEVEL doesn't work either. I suppose there is no harm in just doing that direct to the device, I was just trying to keep it clean and send 100% through the module, but perhaps that was a bad approach.
Thanks,