mouse_opacity bounds bits

ID:895384
 
Jul 28 2012, 3:52 am
Applies to:DM Language
Status: Open
Issue hasn't been assigned a status value.
Currently, I think mouse opacity's 2-setting is based on icon size. Maybe tile size? I dunno, that needs cleared up. Anyway, I figure it might help to be able to specify how mouse clicks are detected; icon size, bounds, or maybe even maptext bounds. This is just in addition to the 2-setting.
Jul 28 2012, 3:54 am
I agree with this as it ties in with my latest request.
Jul 28 2012, 9:51 am
Seen this before; by 'ties in' do you mean you've requested this before or something simular?

Anyway, I'd like to have this aswell.
Jul 28 2012, 10:13 am
I requested to have mouse features work on atoms without an icon if you have maptext on the atom. Mainly for the update on my Turn-Based library, but this request suggests other uses as well.
Aug 17 2012, 7:47 am
 
/*
Current mouse_opacity values:
 0 - invisible
 1 - precise
 2 - imprecise, icon-size-based
Proposed:
 MOUSE_BOUNDS - like 2, but bounds-based
 MOUSE_MAPTEXT - like 1, but for text
 MOUSE_MAPTEXT_BOUNDS - like 2, but maptext-bounds-based

 1 | MOUSE_BOUNDS - redundant
 1 | MOUSE_MAPTEXT - when maptext leaves the icon behind
 1 | MOUSE_MAPTEXT_BOUNDS - redundant

 2 | MOUSE_BOUNDS - redundant
 2 | MOUSE_MAPTEXT - redundant; same as (1 | MOUSE_MAPTEXT)
 2 | MOUSE_MAPTEXT_BOUNDS - redundant

 MOUSE_BOUNDS | MOUSE_MAPTEXT - 
  when maptext leaves the bounding box behind
 MOUSE_BOUNDS | MOUSE_MAPTEXT_BOUNDS - redundant
 MOUSE_MAPTEXT | MOUSE_MAPTEXT_BOUNDS - improbable
 MOUSE_BOUNDS | MOUSE_MAPTEXT | MOUSE_MAPTEXT_BOUNDS - 
  redundant; same as (MOUSE_MAPTEXT | MOUSE_MAPTEXT_BOUNDS)
*/

I wonder if there's a better solution.
Aug 17 2012, 8:00 am
I think it makes sense just to use the bounds instead of the icon size, since it default to the icon size anyway. And when no bounds are present, we could go off map-text bounds.