Hi James.
Either I don’t understand your proposed solution, or you don’t understand the capability I am after. I’m am not sure which it is, at this point… sorry. Please bare with me.
If I have 2 features, and I provide them with a specific location in my map, then, as I zoom-in or zoom-out, the pixel distance between the two features on my screen will change as I zoom, which is obviously the regular, expected behavior. However, I don’t want the regular, expected behavior as I believe there is a HFE/UI need to give the user more context around state of an object, and included with this improved state, a way to independently click on some visual object representing the state.
In other words, I don’t want this pixel difference to change between two “features” as I zoom… both in terms of selection and rendering. I want a multi-part, complex feature with independently rendered, contextually selectable areas that provide the user with a better UI experience. Or… another way of looking at this is… a secondary feature that is always the same number of pixels away from a primary feature, regardless of the zoom-level, etc.
Does my explanation make sense? I’m going to think about this more on my end… maybe there is something I can do with using 1 feature with different rendered bitmaps, and then I could calculate a vector, in pixels, from the feature’s origin and where the user clicked, and compare that against some known location representing a secondary feature to determine what part the user clicked on.
Thanks,
Greg