Hollywood forums

Thanks to your suggestion, I figured out another way to get around the problem. Not perfect, but as long as refresh rate is very high, it works, although not perfectly: @DISPLAY {Width=1920, Height=1080, Title = "MouseEdgeScroller", ScaleMode = #SCALEMODE_AUTO, FitScale = True, Sizeable=Tr...

I noticed Collision check is missing an option to check if a certain spot(X, Y) is colliding, this could be good to add too.
Basically you can use box with width and height of 1 to get this done already, but I suppose it would be faster with actual spot-checking rather than one pixel-sized box.

I am currently planning on having bigger box with a small box in corner on top of the button. Idea here is that by clicking on that bigger box I can load a picture to be displayed on it, but by pushing that small corner box, I can delete the image. Easiest would be to make two #SIMPLEBUTTONs, but ha...

Most of time I use something like this, since by default, something is always changing. Although that 40 hz was just a number I threw in this case to have some number there. I could have used something else in this case instead, but since I by default intend to use it only myself, as long as it work...

Here is a test program to notice the problem and reason for wish: MakeButton(1, #SIMPLEBUTTON, 100, 100, 100, 100, {OnMouseUp=Function() TestText = "A" EndFunction}) MakeButton(2, #SIMPLEBUTTON, 300, 100, 100, 100, {OnMouseUp=Function() TestText = "B" EndFunction}) SetInterval(1,...

I was just about to add functionality to my editor to scroll around by pushing the mouse to the edge of the screen and then moving the screen the amount you are moving your mouse over the edge. But, is there any such command in Hollywood? I can use MouseX and MouseY to get the movement on the screen...

When using StringRequest() with empty body$ part, it makes the stringrequest text space so small you cant read what you are typing: Change to: And it works as its supposed to.

Windows 11 Hollywood 9.1

BeginDoubleBuffer() MakeButton(1, #SIMPLEBUTTON, 100, 100, 200, 200, {OnMouseUp=Function() EndFunction}) DeleteButton(1) will complain "A BGPic needs to be active while calling button functions!" Problem can be got around by turning doublebuffering off before DeleteButton and then back on...

I suppose it is triggered by something, but I don't know by what. I try to keep an eye on it and when it happens, try to recall what I have been doing with the computer.

I know that if I do Box(-1000, -1000, 100, 100, #WHITE) It is not a problem, but Box will simply not be drawn since it is completely outside of screen. But what if I do same with MakeButton? MakeButton(Nil, #SIMPLEBUTTON, -1000, -1000, 100, 100, {OnMouseUp=Function() debugprint("test") End...