+- Charmed Quark Systems, Ltd. - Support Forums and Community (https://www.charmedquark.com/vb_forums)
+-- Forum: General Discussion (https://www.charmedquark.com/vb_forums/forumdisplay.php?fid=3)
+--- Forum: Beta Discussions (https://www.charmedquark.com/vb_forums/forumdisplay.php?fid=12)
+--- Thread: Official 5.3 Beta Discussion Thread (/showthread.php?tid=10397)
RE: Official 5.3 Beta Discussion Thread - kblagron - 06-09-2018
I agree on the scaling thing with WebRIVA.  I have totally turned off my RDP access to CQC, and use the WebRiva access now.  Chrome on the android does not scale it right, and I am now using Fullscreen Browser App, that doesn't scale it right either, but can be adjusted using your fingers.  
As far as my cameras, I have a flag so they will show still images rather than video when WebRIVA is used, and I have an another app on my phone to watch the video (I use the Luxriot software for my cameras).  If I really need to see what is going on I can use that, but usually a still image will suffice for access to CQC.
RE: Official 5.3 Beta Discussion Thread - Dean Roddey - 06-10-2018
I just added a new RIVACmd to let you invoke another browser tab. Put a button on there that you only show when running in WebRIVA that lets you invoke your cam in another tab or something like that. That would make it a bit more convenient. You can give tab a name, so it'll go back to that one if you hit the button again.
RE: Official 5.3 Beta Discussion Thread - kfly - 06-10-2018
Dean,
Not a big deal just curious if you have a hint on where I should look to start my investigation.
I noticed some artifacts around just my buttons in the WebRiva. It started  some time in the mid Beta of WebRiva before it was released.
It only happens on iPads and in both Chrome and Safari. Does not happen on windows Chrome, windows IE, or android Chrome.
Must be an apple/resolution thing but very odd. 
Other than this WebRiva is super solid and very happy with it....
![[Image: bKARZxa.jpg]](https://i.imgur.com/bKARZxa.jpg)
RE: Official 5.3 Beta Discussion Thread - Dean Roddey - 06-10-2018
That's pretty weird. Is the widget big enough to hold the full image? That may be causing some difference. Select those guys and do a Size to Contents in the popup menu and see if that makes a difference.
RE: Official 5.3 Beta Discussion Thread - Dean Roddey - 06-10-2018
Version 5.2.918 is posted. This one takes care of a number of trailing issues that I wanted to get taken care of before the next release. There are some more to do, but I needed to get this out there because the tool bar config dialog got broken by the new publish/subscribe stuff so you couldn't edit toolbars and Bryan needs that for a Pluckers system going in soon.
This should hopefully get the Schlage BE469 lock correctly recognizing lock/unlock notifications. It should fix the RCS thermo V2 driver's issue with parsing the thermo names prompt values. And it should stop incorrectly disabling scene controllers, thinking that they were master/secondary type controllers.
Also, somewhere along the line the IV editor changed from showing info in the status bar about the thing under the mouse and started only showing info for a singly selected widget. Not sure how that happened, but I used the new and improved publish/subscribe stuff to get it back to showing what's under the mouse, which is far more useful.
RE: Official 5.3 Beta Discussion Thread - kfly - 06-10-2018
(06-10-2018, 07:15 AM)Dean Roddey Wrote: That's pretty weird. Is the widget big enough to hold the full image? That may be causing some difference. Select those guys and do a Size to Contents in the popup menu and see if that makes a difference.
and it just gets Weirder..... 
ok I converted the button image back to a PNG file and uploaded here.
https://i.imgur.com/FbJAGAK.png
button is always correct when in chrome with the above link.
If I open up chrome(iPad) and pull up a blank template with just the button it is bad.
If I then open another tab and pull up the link above with just the button and then refresh the first tab(template). it fixes the button on the WebRiva screen(after a refresh)
Is it possible the image cache downloaded from CQC has an issue that is fixed by loading the button from the site above(using request desktop site)?
Only thing they have in common between the WebRiva tab and the imgur image is the name of the .png file downloaded from the two websites.
RE: Official 5.3 Beta Discussion Thread - kfly - 06-10-2018
(06-10-2018, 07:12 PM)kfly Wrote:on second thought the file name changes when I upload to imgur... not sure how the Chrome cache knows the two images are identical so use the good button image from imgur in the WebRiva template....(06-10-2018, 07:15 AM)Dean Roddey Wrote: That's pretty weird. Is the widget big enough to hold the full image? That may be causing some difference. Select those guys and do a Size to Contents in the popup menu and see if that makes a difference.
and it just gets Weirder..... 
ok I converted the button image back to a PNG file and uploaded here.
https://i.imgur.com/FbJAGAK.png
button is always correct when in chrome with the above link.
If I open up chrome(iPad) and pull up a blank template with just the button it is bad.
If I then open another tab and pull up the link above with just the button and then refresh the first tab(template). it fixes the button on the WebRiva screen(after a refresh)
Is it possible the image cache downloaded from CQC has an issue that is fixed by loading the button from the site above(using request desktop site)?
Only thing they have in common between the WebRiva tab and the imgur image is the name of the .png file downloaded from the two websites.
RE: Official 5.3 Beta Discussion Thread - kfly - 06-11-2018
(06-10-2018, 04:23 PM)Dean Roddey Wrote: This should hopefully get the Schlage BE469 lock correctly recognizing lock/unlock notifications. It should fix the RCS thermo V2 driver's issue with parsing the thermo names prompt values. And it should stop incorrectly disabling scene controllers, thinking that they were master/secondary type controllers.
ok loaded the new drop.
looks like the reporting status when I manually flip the lock is backwards. (True should be False,etc)
It is correct if I open/close the lock from the CQC driver.
Just swap the response codes and we should be good. it really reports and show up on the interface fast.
FYI( still had to manually set unit type but no big deal as battery devices are flakey)
RE: Official 5.3 Beta Discussion Thread - Dean Roddey - 06-11-2018
If you do a query info on it, does that work reliably if you do it a few times in a row?
RE: Official 5.3 Beta Discussion Thread - Dean Roddey - 06-11-2018
Yeh, I got them backwards. I flipped them for the next round.