Hi,

I'm trying to change the mouse_map to a resize bmap when over the edge of a panel,

all successful until the mouse_map reaches 0,0 but the spot is at 24,24, meaning i'm unable to move the mouse high enough to click on the panels border,

is there anyway to get around this, or can something be implemented, for the mouse to reach a lower position than 0,0, or aligning the mouse_map so the mouse_spot is always the same as mouse_pos and offseting the image.

Many thanks
MrGuest

Sure, just run a small function that adjusts the mouse_spot value dependent on in which direction the mouse moves.

Hi, I think I may not of explained correctly

If I have create an image, then try rescaling from it's top, I use mouse_spot to do this, easy


But when the edge is already at the top I am unable to move the mouse higher to do this


Adjusting mouse_spot isn't the problem, it's changing it's boundaries which is the problem

Many thanks as always!
MrGuest

The problem is that when you set mouse_spot to a nonzero value, it is not identical anymore with the Windows mouse spot, which is always at the upper left cornder of the pointer image. This means that the Windows mouse position can be already outside the panel when mouse_spot is still inside, and you can't click in that position.

For this reason I suggested to adjust mouse_spot dependent on the move direction. This is a workaround of course, and no real solution. I'll think over an engine fix for this.

yeah workaround i'm using atm, is dragging a different bmap to the -mouse_spot position, and hiding the mouse_map

something similar would be good

This problem has just arisen in another situation.

When creating a crosshair 64x64 the mouse_spot will obviously be 32x32.

If a mouse is clicked at a x or y position less than 32 on the screen position it will either click the border or activate the program behind it.

Moving the crosshair to a negative mouse_spot and having the mouse trigger it it's usual position will solve this.

Any chance of getting this implemented or is it time for another work around?

You can avoid this problem when you not use the predefined mouse_map, but a panel that you move with the mouse, like this:

function bmap_mouse()
{
PANEL* mousepanel = pan_create(NULL,9999);
mousepanel.bmap = some_mousemap;
set(mousepanel,SHOW);
while(1) {
mousepanel.x = mouse_cursor.x + some_offset_x;
mousepanel.y = mouse_cursor.y + some_offset_y;
wait(1);
}
}

Then you can leave mouse_spot at zero and it should still work, try it.

Thanks Spirit for this but I've already implemented pretty much that as said in previous posts . What I'm asking for is to not have to use a work around for such a simple thing. It's obvious and been acknowledged there's a problem with using mouse_spot the way it is at the moment so wondering why it's still the way it is and not having it fixed when one could easily be implemented.

Yes, you certainly have a point. I'll put this on our priority list for the next update.

Thanks JCL!