[Script] WME Place Interface Enhancements

[JustinS83]

@rompompom

While working through the EVCS feed, I noticed that, with some of the GM POIs quite a distance away from the actual charging station, the distance that PIE gives when the GM POI is not in the map view, is vastly different from distance measured with WME’s ruler tool. See picture below.

Is there some kind of unit conversion going awry? 398 divided by 247 is 1.611; roughly the mile / km ratio.

Thank you for the report, we are looking into it - not related to metric vs imperial but it will be fixed soon.

[dinohoo]

Having an issue where after selecting a PUR, any element that is selected ie. segments/places will show as “No address” in the data fields. Had to refresh the page to see everything normally if this happens. Also when entering data in the General and More Info tabs, if the changes are not saved and you switch tabs, you would have to reenter the data. Not always reproducible, seems like it occurs randomly. Confirmed that PIE is the culprit since all these issues did not reoccur after deactivating this script.

Happy to provide anything else if needed

[JustinS83]

@dinohoo

Confirmed that PIE is the culprit since all these issues did not reoccur after deactivating this script.

This is correlation, not causation. If PIE is the only script running and this occurs, and does not occur when PIE is not running, that is confirming

I just tested what you described:

1. Select a place or segment
2. Select a PUR
3. “No address” will display in the data fields

I could not reproduce your results.

The following did produce the described results, however.

1. Select a place or segment
2. Select a PUR
3. Reject or Approve the PUR
4. Save
5. Deselect the place or segment
6. Re-select the place or segment
7. “No address” will display in the data fields.

I was able to produce the described bug using the steps above, with no scripts running. This is a WME bug, not a PIE bug.

[dinohoo]

@JustinS83

@dinohoo

Confirmed that PIE is the culprit since all these issues did not reoccur after deactivating this script.

This is correlation, not causation. If PIE is the only script running and this occurs, and does not occur when PIE is not running, that is confirming

I just tested what you described:

1. Select a place or segment
2. Select a PUR
3. “No address” will display in the data fields

I could not reproduce your results.

The following did produce the described results, however.

1. Select a place or segment
2. Select a PUR
3. Reject or Approve the PUR
4. Save
5. Deselect the place or segment
6. Re-select the place or segment
7. “No address” will display in the data fields.

I was able to produce the described bug using the steps above, with no scripts running. This is a WME bug, not a PIE bug.

Welp I stand corrected then, I don’t mean to drop any accusations, but I do admit I’m not that well versed with all these code stuff and it so happened that I’ve not had it happen when no scripts are running haha. Thanks for your effort in busting my myth this quick, let’s hope the bug is fixed soon then

[JustinS83]

Welp I stand corrected then, I don’t mean to drop any accusations, but I do admit I’m not that well versed with all these code stuff and it so happened that I’ve not had it happen when no scripts are running haha. Thanks for your effort in busting my myth this quick, let’s hope the bug is fixed soon then:)

It’s all good my dude - no offense was taken! Just demonstrating that further testing is necessary before pointing and saying “this is a script bug!”

[dinohoo]

@JustinS83

Welp I stand corrected then, I don’t mean to drop any accusations, but I do admit I’m not that well versed with all these code stuff and it so happened that I’ve not had it happen when no scripts are running haha. Thanks for your effort in busting my myth this quick, let’s hope the bug is fixed soon then:)

It’s all good my dude - no offense was taken! Just demonstrating that further testing is necessary before pointing and saying “this is a script bug!”

I thought I did enough testing but evidently I could’ve done more - will definitely dive deeper next time!

[jasawebsite]

@JustinS83

@dinohoo

Confirmed that PIE is the culprit since all these issues did not reoccur after deactivating this script.

This is correlation, not causation. If PIE is the only script running and this occurs, and does not occur when PIE is not running, that is confirming

I just tested what you described:

1. Select a place or segment
2. Select a PUR
3. “No address” will display in the data fields

I could not reproduce your results.

The following did produce the described results, however.

1. Select a place or segment
2. Select a PUR
3. Reject or Approve the PUR
4. Save
5. Deselect the place or segment
6. Re-select the place or segment
7. “No address” will display in the data fields.

I was able to produce the described bug using the steps above, with no scripts running. This is a WME bug, not a PIE bug.

it seems that this is a WME bug and not a PIE bug, which is helpful information for anyone who may come across this issue in the future.

[linguasaltitante]

Hello

When I have PIE enable the strings “Create point” and “Create area” aren’t show localized on menu create places:

With PIE enable

With PIE disable
(in this case, properly show localized to portuguese-Portugal)

Thanks

[G_W1Z]

With the latest version of PIE and today’s WME production release the top bar disappears once you pan around on the map (amongst other actions in WME.)

Here is a screen capture of how it looks:

[searchjaunt]

@G_W1Z

With the latest version of PIE and today’s WME production release the top bar goes dead once you pan around on the map. Here is a screen capture of how it looks:

Having the same issue. It happens all the time: resizing a window, selecting a segment, adding a closure, …

[DownPeriscope]

@G_W1Z

With the latest version of PIE and today’s WME production release the top bar goes dead once you pan around on the map.

No need to pan around for this effect. Simply selecting a segment or place on the map suffices for me.

I hope it gets fixed soon…

[Jorge-RC]

@G_W1Z

With the latest version of PIE and today’s WME production release the top bar goes dead once you pan around on the map. Here is a screen capture of how it looks:

Same problem here when refreshing Issue left panel

[jm6087]

@Jorge-RC

@G_W1Z

With the latest version of PIE and today’s WME production release the top bar goes dead once you pan around on the map. Here is a screen capture of how it looks:

Same problem here when refreshing Issue left panel

It is a known issue. I am sure Justin will have it back up and running in due time.

[DownPeriscope]

@jm6087

@Jorge-RC

@G_W1Z

With the latest version of PIE and today’s WME production release the top bar goes dead once you pan around on the map. Here is a screen capture of how it looks:

Same problem here when refreshing Issue left panel

It is a known issue. I am sure Justin will have it back up and running in due time.

This would be so much more comforting if any of us would know when that “due time” could be…

(And if Justin should read this: please take it as the compliment it implies. We fully realise that your life doesn’t revolve around fixing a script for us. But we miss your script and would rather have it back yesterday. It it were crap, we wouldn’t moan so much. And I for one can’t code my way out of a paper bag, so I need your kind help and mastery to stop me (and the people suffering silently in the background) from sobbing at the keyboard.)

[jm6087]

@DownPeriscope

@jm6087

@Jorge-RC

Same problem here when refreshing Issue left panel

It is a known issue. I am sure Justin will have it back up and running in due time.

This would be so much more comforting if any of us would know when that “due time” could be…

(And if Justin should read this: please take it as the compliment it implies. We fully realise that your life doesn’t revolve around fixing a script for us. But we miss your script and would rather have it back yesterday. It it were crap, we wouldn’t moan so much. And I for one can’t code my way out of a paper bag, so I need your kind help and mastery to stop me (and the people suffering silently in the background) from sobbing at the keyboard.)

I can define “due time”

:mrgreen: “due time” = when Justin has time and desire to dig into the code, fix it, and publish it :mrgreen:

I am not able to narrow it down much more that that.

[ehepner1977]

I can also categorically state that asking for ETAs will increase the amount of time. Whether it’s intended, or not, asking for an ETA comes off as entitlement.

[JustinS83]

Hey all,

Thanks for the patience. There have been substantial changes to the native place menu, and it would appear that something with changing also (for SOME FRICKIN REASON) causes issues with the issue tracker if something isn’t found in the place menu correctly. There is a substantial chance customization of the place menu will have to be removed, and you will have to revert to the (stupid) native menu where you can only set main categories.

Sorry

[krzycholub]

@JustinS83

Hey all,

Thanks for the patience. There have been substantial changes to the native place menu, and it would appear that something with changing also (for SOME FRICKIN REASON) causes issues with the issue tracker if something isn’t found in the place menu correctly. There is a substantial chance customization of the place menu will have to be removed, and you will have to revert to the (stupid) native menu where you can only set main categories.

Sorry

Fingers crossed!

[DownPeriscope]

@ehepner1977

I can also categorically state that asking for ETAs will increase the amount of time. Whether it’s intended, or not, asking for an ETA comes off as entitlement.

You could say that. You’d be wrong, though.

[JustinS83]

@DownPeriscope

@ehepner1977

I can also categorically state that asking for ETAs will increase the amount of time. Whether it’s intended, or not, asking for an ETA comes off as entitlement.

You could say that. You’d be wrong, though.

No, he is 100% correct. If I get hounded for ETAs for when something will be fixed, I will 100% ignore TF out of working on it and just point those asking to the github repository where you can submit pull requests with the fixes.