jm6087 wrote: ↑Mon Aug 02, 2021 11:01 pm

SeveriorumPatrem wrote: ↑Mon Aug 02, 2021 1:34 pm Has it ever been brought up or requested....?

I love the function of PIE when creating an RPP how it can auto-populate street and city based on nearby segments.  However, sometimes you're at a zoom level where you place an RPP and there are no segments within range to derive street info from.  When this occurs, the RPP is created but the side panel remains unchanged, and you then have to click to select the new RPP and then click into the details fields to define an address.

So, if it hasn't been requested before, and is a reasonable request, can we get PIE to open the RPP addressing panel and place the cursor in the house number field, upon creation of a new RPP where no existing street data is available to derive from nearby segments?


 

Do you mean something like this?



Activate "Edit RPP address after created"
 

 

jm6087 wrote: ↑Tue Aug 03, 2021 11:36 am Same thing


 

 

russblau wrote: ↑Thu Mar 16, 2023 5:07 pm I can no longer create new places with PIE running. To make sure this was the cause, I disabled all other scripts.  Following is the console error message:

Code: Select all

Uncaught TypeError: Cannot read properties of null (reading 'name')
at Model.getStreetName (WazeWrapLib.js?_=1678986320190:616:66)
at Geometry.findClosestSegment (WazeWrapLib.js?_=1678986320190:592:45)
at createPlace (userscript.html?name=WME%2520Place%2520Interface%2520Enhancements.user.js&id=a5521725-bb88-4960-b15f-b7aa86c4e48b:5904:44)
at endPlacementMode (userscript.html?name=WME%2520Place%2520Interface%2520Enhancements.user.js&id=a5521725-bb88-4960-b15f-b7aa86c4e48b:5851:9)
at HTMLDivElement.<anonymous> (userscript.html?name=WME%2520Place%2520Interface%2520Enhancements.user.js&id=a5521725-bb88-4960-b15f-b7aa86c4e48b:5734:50)
at HTMLDivElement.dispatch (third_party-912caaccb7609d06b745.js.gz:2:1348154)
at g.handle (third_party-912caaccb7609d06b745.js.gz:2:1346149)

 
 

 

rompompom wrote: ↑Tue Apr 11, 2023 2:17 pm 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.


 
 

 

dinohoo wrote: ↑Wed Apr 12, 2023 4:43 pm Confirmed that PIE is the culprit since all these issues did not reoccur after deactivating this script. 

 

 

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:)

DownPeriscope wrote: ↑Sun Jun 11, 2023 9:14 am

ehepner1977 wrote: ↑Sat Jun 10, 2023 6:57 pm 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. 
 

 

DownPeriscope wrote: ↑Mon Jun 12, 2023 12:16 pm

JustinS83 wrote: ↑Mon Jun 12, 2023 12:38 am

DownPeriscope wrote: ↑Sun Jun 11, 2023 9:14 am

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.
 

 

I'm sorry, Justin, but could you please point out to me, how you think I was hounding you?
 
 

 

rompompom wrote: ↑Tue Jul 18, 2023 12:42 pm Thanks for the update. One issue still remaining on my end is that I can type in the opening hours in the box for opening times of a plce, but clicking add hours or replace hours doesn't have any effect.