Hi Alessandro, One can put the select menu also over the map, so it's more visible. Modifications of this sort as well as animations are typically part of customizations. There is rarely one golden way how to achieve a goal. Some like animations, some don't.
if one starts with dis/enabling buttons, then where to start and where to stop? One could disable also zoomin/out when max/min reached, back/fwd button when history exceeded, also identify and tooltips just if there are queryable layers. This would require a full set of update mechanisms and their definition. And at the end I wonder if it is more confusing if half of the buttons are disabled at the beginning... The double call is - as Walter discovered - related to a double call both via onmousedown and onclick. The reason for having this was related to usage consistency. This was years in the past so I just recall vaguely that there was a potential problem with a user clicking on a button and moving in or out, and then active button and tool mode could have been different. The workaround with double call removed this and I kept it. In your case where you want to draw attention to something happening, maybe a double animation draws even more attention ;-) Armin Alessandro Pasotti wrote: > Il giovedì 28 giugno 2007, Armin Burger ha scritto: >> At least in the current version 3.1 this seems not to be the case. It >> does not hurt very much to have it called twice, though... > > I'm addressing usability, trying to improve it, and one of the problem I've > seen is that users don't notice that the "select" tool is bound to a > particular layer because the select control is very small. Another problem > arises when no queryable layers are active, the user should be warned somehow > that cannot use the "select" tool in those cases (maybe disable the tool?). > > So I've added a warning message in the select DIV in case no options for the > select are returned in x_select.php , and a simple slideIn animation to draw > user attention to the select DIV area. > > Sorry for the long explanation, but if x_select is called twice, the > animation > also play twice, and this is not so nice. > > Anyway, if you are sure 3.1 doesn't call x_select twice I will run diff > against it on all js files and see if some critical parts have changed. > > Perhaps we should join our efforts in order to improve pmapper usability, I > don't think it need heavy refactorying, just a few small enhancements. > > Thanks. > ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ pmapper-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/pmapper-users
