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. -- Alessandro Pasotti itOpen - "Open Solutions for the Net Age" w3: www.itopen.it Linux User# 167502 ------------------------------------------------------------------------- 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 pmapper-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/pmapper-users
