Marker Collision processing broken in v3.0.6
joe-shapiro-biz opened this issue · 15 comments
joe-shapiro-biz commented
with latest release, getting the above error in console. Note case of "optionaL_"
valentasm1 commented
Could you give a bit more information?
joe-shapiro-biz commented
Blazor wasm project.
Error occurs while drawing initial markers, with clusterer.
Does not happen in production .net 6 environment but does in dev .net 7 environment.
This is the code…
var opts = new MarkerOptions()
{
Label = label,
Visible = MarkerVisible,
Position = position,
Clickable = true,
// jds THIS ONE
CollisionBehavior = CollisionBehavior.REQUIRED_AND_HIDES_OPTIONAL,
ZIndex = 99,
Map = _Map.InteropObject,
Icon = icon,
Title = Title
};
var mk = await Marker.CreateAsync(_Map.JsRuntime, opts);
From: Valentas ***@***.***>
Sent: Wednesday, May 31, 2023 11:51 AM
To: rungwiroon/BlazorGoogleMaps ***@***.***>
Cc: Joe Shapiro ***@***.***>; Author ***@***.***>
Subject: Re: [rungwiroon/BlazorGoogleMaps] setCollisionBehavior: optionaL_AND_HIDES_LOWER_PRIORITY is not an accepted value (Issue #263)
Could you give a bit more information?
—
Reply to this email directly, view it on GitHub<#263 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEE4OLOTRPXEM72B7GU6GITXI5SHDANCNFSM6AAAAAAYVVF2ZQ>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
valentasm1 commented
Sorry but unable to reproduce with our wasm sample nor in .net 6, nor .net 7.
Would need minimal project
joe-shapiro-biz commented
Project works with v2.5.7, fails with v3.0.6
I will try to find the time to create a minimal project.
From: Valentas ***@***.***>
Sent: Wednesday, May 31, 2023 1:02 PM
To: rungwiroon/BlazorGoogleMaps ***@***.***>
Cc: Joe Shapiro ***@***.***>; Author ***@***.***>
Subject: Re: [rungwiroon/BlazorGoogleMaps] setCollisionBehavior: optionaL_AND_HIDES_LOWER_PRIORITY is not an accepted value (Issue #263)
Sorry but unable to reproduce with our wasm sample nor in .net 6, nor .net 7.
Would need minimal project
—
Reply to this email directly, view it on GitHub<#263 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEE4OLMLRLVDX3DKD74GXLTXI52QFANCNFSM6AAAAAAYVVF2ZQ>.
You are receiving this because you authored the thread.Message ID: ***@***.******@***.***>>
joe-shapiro-biz commented
required.zip
run this and look at the javascript console.
then comment out this line in Map.razor and do it again...
CollisionBehavior = CollisionBehavior.REQUIRED_AND_HIDES_OPTIONAL,
joe-shapiro-biz commented
(and, of course, the collision processing does not work under these circumstances)
valentasm1 commented
I think it come down from &v=beta . It should be &v=3
Sorry but i dont want to try make it work with beta version. Who knows. Maybe with production version it will start working
valentasm1 commented
Also thank you for demo project. I know it takes time
joe-shapiro-biz commented
Marker collision is only available in v=beta. V=3 turns off the feature altogether, hiding the problem.
…________________________________
From: Valentas ***@***.***>
Sent: Sunday, June 4, 2023 1:50:05 PM
To: rungwiroon/BlazorGoogleMaps ***@***.***>
Cc: Joe Shapiro ***@***.***>; Author ***@***.***>
Subject: Re: [rungwiroon/BlazorGoogleMaps] Marker Collision processing broken in v3.0.6 (was optionaL_AND_HIDES_LOWER_PRIORITY ) (Issue #263)
Also thank you for demo project. I know it takes time
—
Reply to this email directly, view it on GitHub<#263 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEE4OLJOBATRU4WFXKZNSKDXJTDE3ANCNFSM6AAAAAAYVVF2ZQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
joe-shapiro-biz commented
…
________________________________
From: Joe Shapiro ***@***.***>
Sent: Sunday, June 4, 2023 2:04:54 PM
To: rungwiroon/BlazorGoogleMaps ***@***.***>; rungwiroon/BlazorGoogleMaps ***@***.***>
Cc: Author ***@***.***>
Subject: Re: [rungwiroon/BlazorGoogleMaps] Marker Collision processing broken in v3.0.6 (was optionaL_AND_HIDES_LOWER_PRIORITY ) (Issue #263)
Marker collision is only available in v=beta. V=3 turns off the feature altogether, hiding the problem.
________________________________
From: Valentas ***@***.***>
Sent: Sunday, June 4, 2023 1:50:05 PM
To: rungwiroon/BlazorGoogleMaps ***@***.***>
Cc: Joe Shapiro ***@***.***>; Author ***@***.***>
Subject: Re: [rungwiroon/BlazorGoogleMaps] Marker Collision processing broken in v3.0.6 (was optionaL_AND_HIDES_LOWER_PRIORITY ) (Issue #263)
Also thank you for demo project. I know it takes time
—
Reply to this email directly, view it on GitHub<#263 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEE4OLJOBATRU4WFXKZNSKDXJTDE3ANCNFSM6AAAAAAYVVF2ZQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>
valentasm1 commented
Related
#127
valentasm1 commented
Thank you for not giving up. There was huge migration from json.net to system.text.json so in that step it was lost some enum serializations.
https://www.nuget.org/packages/BlazorGoogleMaps/3.0.7
joe-shapiro-biz commented
Thank you
…________________________________
From: Valentas ***@***.***>
Sent: Friday, June 9, 2023 3:34:26 AM
To: rungwiroon/BlazorGoogleMaps ***@***.***>
Cc: Joe Shapiro ***@***.***>; Author ***@***.***>
Subject: Re: [rungwiroon/BlazorGoogleMaps] Marker Collision processing broken in v3.0.6 (Issue #263)
Thank you for not giving up. There was huge migration from json.net to system.text.json so in that step it was lost some enum serializations.
https://www.nuget.org/packages/BlazorGoogleMaps/3.0.7
—
Reply to this email directly, view it on GitHub<#263 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AEE4OLMZ2JMDCQTMXYDTWV3XKLGYFANCNFSM6AAAAAAYVVF2ZQ>.
You are receiving this because you authored the thread.Message ID: ***@***.***>