No, not using a Gaticule Layer... just regular InMemoryFeatureLayers.
Let me ask my question another way...
Let's say I load a raster and worldfile that is north up (ie rotation values in worldfile are 0). Let's also say I write a MouseMove event handler that takes the mouse location and shows the current Lat/Long. In that case, as I move the pointer around to various points on the raster, the results of the MouseMove handler show the true Lat/Long of features on the raster. I understand that the raster layer really has nothing to do with this (tho the world file that came with it certainly did)
Now let's say that my raster is not north up (ie rotation values not 0). North actually points off the right side of the screen. In this case, the Lat/Long is only correct for one pixel... the upper-left pixel. As I move the pointer around now, the reported Lat/Long is totally incorrect. As I move to the right, the location shows a decreasing Long instead of an increasing Lat.
I understand why. The calculation that the Map class is using to convert pixel to map coordinate is doing a simple pixel.x * pixel_width calculation with the pixel width from the world file. It is ignoring the y component of pixel width (rotation value). It is the same case for movement in the y direction.
My customer is hading me rasters that are rotated off true north. When I read them in, I really need for the Map control to pay attention to the rotation values so that when it converts pixels to coordinates it stays 'with' the raster.
I understand the raster is just a dumb image in the background. I just need to know how to tell the Map control to run its 'internal grid' in something other than a rigid up/down left/right orientation.
Thank you for your time,
Dave