Hi Brian, I now have the proof that mergAV DOES in fact needs global coordinates. Thanks for that, Matthias!
This (as found in the dictionary) gives you the offset: ... mergAVCamSet "rect",the rect of graphic "qr_ios" ... However THIS is neccessary to make it work correctly: ... put the topleft of grc "qr_ios" into tRect1 put the bottomright of grc "qr_ios" into tRect2 put globalloc((tRect1)) & "," && globalloc((tRect2)) into tRect mergAVCamSet "rect",tRect ... I really wonder why noone noticed this before!? Will create a bug report for thhis later this evening. > Am 15.11.2022 um 14:38 schrieb Klaus major-k via use-livecode > <use-livecode@lists.runrev.com>: > > Hi Brian, > >> Am 15.11.2022 um 14:29 schrieb Brian Milby via use-livecode >> <use-livecode@lists.runrev.com>: >> >> I know that inside any native control, things are drawn at native >> resolution. A good way to see this is a browser widget. So I’m thinking >> that that is going to apply in the other direction too. You will need to >> convert your card coordinates to native coordinates to place the control. > Then this should go into the dictionary with 128 point fontsize! THIS! >> I might could play with the math, but it wouldn’t be until much later this >> evening. > ... >> Brian Milby >> br...@milby7.com Best Klaus -- Klaus Major https://www.major-k.de https://www.major-k.de/bass kl...@major-k.de _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
