Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Z-Index of place mark has different results #64

Closed
dave-barrineau opened this issue Nov 17, 2016 · 4 comments
Closed

Z-Index of place mark has different results #64

dave-barrineau opened this issue Nov 17, 2016 · 4 comments
Labels

Comments

@dave-barrineau
Copy link

dave-barrineau commented Nov 17, 2016

I submitted a question on the Forum but no replies and this looks to be a bug. Here is the content of the forum post (http://forum.worldwindcentral.com/showthread.php?46248-Set-z-index-of-a-place-mark&p=125652#post125652) EDIT: Link is no longer valid:

"The app I'm building can have overlapping place marks. When the user clicks on one that is behind another I want to bring the selected place mark to the top. (I have a sprite place mark that renders a border around an image of a place mark.) I've tried setting alwaysOnTop to true but that does not work. I also have tried setting the eyeDistance to a very small number (everywhere from 0 to 10) separate and in conjunction with the alwaysOnTop. I recompiled the Web World Wind library to not uglify (option passed to requirejs) and when setting eyeDistance and alwaysOnTop, it does work. However the uglified version does not."

** On the forum post I have two images of the uglified vs. non-uglified results.

@pdavidc pdavidc added the bug label Dec 22, 2016
@dave-barrineau
Copy link
Author

What's the status of this issue? My project is getting to a point where we're going to need this fixed. Thanks.

@pdavidc
Copy link
Contributor

pdavidc commented Feb 22, 2018

@dave-barrineau The distinction about the RequireJS uglify option sounds suspicious. Have you tried using Placemark.alwaysOnTop with the 0.9.0 release library?

@dave-barrineau
Copy link
Author

@pdavidc This appears to be fixed with 0.9.0 release (we just stepped up to this release a few weeks ago). Therefore you can close this ticket. If for any reason we happen to see it again I'll open a new ticket. Thanks --Dave

@ghost ghost removed the standalone label Feb 23, 2018
@pdavidc
Copy link
Contributor

pdavidc commented Feb 23, 2018

Thanks, @dave-barrineau!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Development

No branches or pull requests

2 participants