Mouse cursor offset/SNAPSHOT timeout

[deleted-user-VeZur_n9o0OZ]

Hey guys,

Quick one...has anybody experienced an offset curser when using tools such as zoom and box select?
For example, I click to draw a rectangle around some features and the box begins to draw a number of pixels away. My spatial ref of all feature layers is 3857 (WGS84 MAS) same as the basemaps. Anyone know a quick fix for this?

For a bonus point: I'm using a SNAPSHOT feature layer to return 4000+ records (time enabled). I've had to cut this down to 3000 as my GET request seems to timeout and return no features otherwise. Can i increase the timeout time? Seems to die after 15secs in firebug. I've tried changing the pooling params with no success in manager.

Thanks all,
James

[derekswingley1]

Hi James,

The first issue you're describing is usually CSS related. It's hard to say exactly what's happening without seeing your markup and CSS.

Your layer timing out should be a red flag. You can increase the default timeout but I would caution against this for a couple of reasons:
-do you want to make your users wait 15-20s(or longer?) for your app's data to load?
-displaying 3-4k features in any browser will likely cause noticeable performance issues

There are a couple of ways to address this:
-start your app at a larger scale so less features are displayed
-use scale dependencies and a dynamic map service to show your data

[ChadWilcomb]

James, did you ever figure out your first question here? I am having the same issue and coincidentally I am also using a FeatureLayer select (although this issue appears before the selection).

[deleted-user-VeZur_n9o0OZ]

Hey I'm afraid not. I still see a cursor offest from time to time in my apps. More often in Chrome than other browsers. Did you find a fix?

[ChadWilcomb]

I was able to solve the cursor offset issue by using map.reposition() after any change in my page layout that affected the map div.

Hey I'm afraid not. I still see a cursor offest from time to time in my apps. More often in Chrome than other browsers. Did you find a fix?