Hollywood forums

There seems to be a problem with buttons being detected in the correct location when using RapaGUI with Fitscale and KeepProportions set to "True." The vertical placement seems to be correct, but the horizontal placement is wrong. (The same problem shows up whether #LAYERBUTTON or #SIMPLEB...

I can't test this right now, but I think the way I've done it before was to replace "[" with "[[" and replace "]" with '']]" (double brackets).

Revisiting an issue that has been troubling me for a while now... The following code fixes the proportional scaling issue (kind of). But the problem is that it requires a SystemRequest() message to be used. Without the message, the scaling is wrong (too long in Portrait mode and too short in Landsca...

Constants such as #ATTRWIDTH and #ATTRHEIGHT have number values assigned to them (0 and 1 respectively). DebugPrint(#ATTRWIDTH, #ATTRHEIGHT) But when you weren't using the constants, ATTRWIDTH and ATTRHEIGHT were taken as variables that had not yet been assigned a value, so they were equal to zero (...

Your code is a bit wrong.
Try this instead:

I think the problem might be solved by delaying things like moai.get("Main", "Height") and GetAttribute(#DISPLAY, 1, #ATTRSCALEHEIGHT) until after the display has settled on its new attributes. It seems like the numbers are different initially (when first started and right after ...

It probably goes back to the Hollywood 8 version of the Android player.

With the newest RapaGUI (and Hollywood Player for Android), the code that worked before has a couple problems now. I found a workaround for one of the problems by delaying the first scaling using SetTimeout(), though there's probably a better way of handling that. (See code below.) However, the scal...

Yes, RunCallback() does work and is better. Thanks for the suggestion!
(I keep forgetting to use that new function.)

If it's a hard one to fix, this might be a good enough work-around: @REQUIRE "RapaGUI" Function p_CustomErrorMessage(msg) SystemRequest("Debug Output", "Code: "..msg.userdata[0].."\nString: "..msg.userdata[1].."\nCommand: "..msg.userdata[2].."\n...