-
Notifications
You must be signed in to change notification settings - Fork 467
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
FontSymbol cannot display different symbol (ol ext 4.0.24, work with OL 10.2.1, not 10.3.1) #1123
Comments
Just publish [email protected]. |
it seems to work in the codesandbox, il will try te update my code on next monday. thank you |
I update my sandbow with a non-working example, two features with same fill color, same symbol but different stroke colors are shown with the same stroke color I think it from createRenderOptions witch doesnt provide the stroke color in the key, as they problably didn't need it, openlayers dev's didn't neither use it in the key and i think the provider canvas for both symbols is the same and before drawing, the context.strokeStyle is the same for both Symbol Maybe you can update the createRenderOptions with all your needed options I tried to extend your class and it seems to work: Ps: Sorry i don't have the time to contribute with a PR |
I've added the line stroke keys to the render options |
thank you, i will wait for the 4.0.26 :) |
Hi, Sorry to bother you, but do you plan tu publish a new package soon? Thank you |
Just published v4.0.26 |
updated my example, seems to work :) |
Hi,
It seems OpenLayers changed theyr render method, using different FontSymbol doesn't work
In my examples i have two features and i use a getSyle method wich switch between two icons, depends ont feature "test" property
working example with ol10.2.1:
https://codesandbox.io/p/sandbox/ky98xz
Not working example with ol10.3.1:
https://codesandbox.io/p/sandbox/animated-gif-forked-npv8vy
I was looking in your commits since 4.0.24 release (especially 6ea333d) , maybe you already patch it? If so, do you plan to release au new version soon?
thank you,
David
The text was updated successfully, but these errors were encountered: