> > 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... > > Is this not the normal way the GUIs works? > But I understand it requires a lot of work.
GUI's of a desktop application, yes. > > > > 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. > > So, do you think is dangerous to apply the Walter's patch and it could > lead to > problems? there is nothing dangerous, you will not lose your data ;-) As I said, I added this once to avoid inconsistencies in rare cases of clicks and keeping mouse pressed and release it. I don't know any more the exact combination since it's years ago. Armin -- Psssst! Schon vom neuen GMX MultiMessenger gehört? Der kanns mit allen: http://www.gmx.net/de/go/multimessenger ------------------------------------------------------------------------- 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
