510.1320 - Click events stopped working on images

Page: 1 2
ID:2025753
 
Jan 27 2016, 7:03 pm (Edited on Jan 27 2016, 7:17 pm)
Not a bug
BYOND Version:510
Operating System:Windows 7 Pro 64-bit
Web Browser:Chrome 48.0.2564.82
Applies to:Dream Seeker
Status: Not a bug
This is not a bug. It may be an incorrect use of syntax or a limitation in the software. For further discussion on the matter, please consult the BYOND forums.
Descriptive Problem Summary:
None of the click events are working in my latest project after upgrading to 510.

Click(), Drag, MouseDown, and etc aren't registering mouse events on images I have associated with objects. Known issue in 510?

Jan 27 2016, 7:05 pm
Client() is registering clicks.
Jan 27 2016, 7:35 pm
Lummox done good this time broke everything with 510 I'm guessing he didnt actually test the new things he added or edited for 510 xD
Jan 27 2016, 7:40 pm
In response to Zasif
Zasif wrote:
Lummox done good this time broke everything with 510 I'm guessing he didnt actually test the new things he added or edited for 510 xD

I tested quite a bit, but lots of stuff shows up in bigger games that doesn't show up in smaller test projects. Plus this is just a beta, and the goal was to get the beta out to people right away. Patience.
Jan 27 2016, 7:46 pm
Let me know if you need a repro. Hoping you can repro it easy enough before I spend time reducing the project down to a repro.
Jan 27 2016, 7:51 pm
Actually, I just ran a number of other projects using similar functionality and they're working ok. Let me poke around some more. Something about this particular project is at fault.
Jan 27 2016, 7:54 pm
Okay, cool. With a bug of this complexity I won't be getting to it till tomorrow anyway so if you can get something together that shows the issue, I'll be glad to take a look then.
Jan 27 2016, 8:14 pm
Is this the same issue I messaged you about? Wasn't sure at the time if I was just doing it wrong or it was a bug.
Jan 27 2016, 8:29 pm
No idea yet. I need a test case to look at.
Jan 27 2016, 8:30 pm
I thought for sure I sent you one, hold on a few while I finish fiddling with it.
Jan 27 2016, 8:31 pm
Oh, right, I do see code there. A full project would probably be more useful as I can simply run that quickly. I'll look into it tomorrow.
Jan 27 2016, 8:32 pm
Yeah, thought I sent the project files to your mail but I never hit send.
Jan 27 2016, 10:53 pm
Can confirm. As well, when modifying the transform of a plane master all mouse detection seems to stop.

Not sure if it's part of the same problem or not so I didn't want to make a new thread.
Jan 27 2016, 11:04 pm
I'd make a new thread for the transform issue; I know why that's happening but it's definitely separate.
Jan 27 2016, 11:05 pm
In response to Lummox JR
Lummox JR wrote:
I'd make a new thread for the transform issue; I know why that's happening but it's definitely separate.

Will do.
Jan 28 2016, 3:44 pm
Nadrew, it turns out your issue actually does dovetail with Bravo's. However I'm not certain it's the same issue that PopLava was having, so I'm going to leave this open.
Jan 28 2016, 9:29 pm
Confirmed the click event works in 509 but not in 510. I think it has something to do with the syntax in client/New().

repro files
Jan 29 2016, 8:57 am
Lummox JR resolved issue (Not a bug)
Jan 29 2016, 8:59 am
I found the issue, and it's not anything wrong with clicks. This is the HUD layering change in action. Your image is showing up below the HUD.

I recommend setting your HUD's plane to -1, which will make the issue go away. The next release will also allow the use of BACKGROUND_LAYER in topdown worlds, and that will work too. Making the screen controls HUD objects themselves is yet another (probably preferable) solution. A fourth solution is making the HUD mouse-transparent.
Jan 30 2016, 11:05 am
Can you elaborate some more? The layer was already set to -1 and the mouse_opacity needs to be opaque so drag operations work properly by always being under the mouse.

Also, why didn't you suggest the use of plane in this scenario? Is there a reason why I might not use it here?

        screen += new /atom/movable {
            name = ""
            layer = -1#INF
            //plane = -100
            mouse_opacity = 2
            screen_loc = "SOUTHWEST to NORTHEAST"
        }
Page: 1 2