2 comments. First, do I read this correctly that you are updating each move every time the user hits the arrow key? If so, don't do that. Let the user click once where they want it to go and move it once.
Second, 250 indexed records should be smoking fast. Are you sure you have the code written efficiently and the database optimized? Martin Morrison Application Engineer Engineering Design Systems, Inc. 3780 Peters Creek Rd Ext SW Roanoke, VA 24018 540.345.1410 gis.edsi.com -----Original Message----- From: mapguide-users-boun...@lists.osgeo.org [mailto:mapguide-users-boun...@lists.osgeo.org] On Behalf Of tmblackflag Sent: Wednesday, November 09, 2011 12:13 PM To: mapguide-users@lists.osgeo.org Subject: [mapguide-users] Re: Client side way to get FEATID's from FDO? FEATID is an identity property and lives in a RDBMS. It is a primary key and is indexed and table is only 250 records right now. It takes a total of 7-8 seconds to post to the db, get the feat id, then connect to the DB to update the coordinates for the associated label point. What i was really trying to do was give them 4 directional arrows so they could move label points as they please. Since this is slower, I may have them select the label point they want to move, then digitize a new landing point and then update the existing record. That would probably be faster than using arrows to move the point a few x/y coordinates at a time. -- View this message in context: http://osgeo-org.1803224.n2.nabble.com/Client-side-way-to-get-FEATID-s-from-FDO-tp6976596p6978659.html Sent from the MapGuide Users mailing list archive at Nabble.com. _______________________________________________ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users _______________________________________________ mapguide-users mailing list mapguide-users@lists.osgeo.org http://lists.osgeo.org/mailman/listinfo/mapguide-users
