Works well with the Dec 19 editor release. There is still some functionality challenges with the highlighter script. As the map is panned, the highlighter script dynamically updates the menus for editors and cities. When WMECH is integrated into WazeBar, these dynamic updates don't happen. Permalink needs to be hit first. And even then, for some reason, the WazeBar version of the city menu, for example, doesn't contain the same values, such as same city/different state.

Other functions of WB are working very nicely for me. I am using WMECH in non-integrated mode and it's extremely nice to have. With the recent cap on 150 edits which count for points per save, the auto-save feature is very nice to have. It still surprises me, but probably "saves" me from losing points. I'd like to see the slider be able to be adjusted higher, maybe 150, even though there is no direct relationship between changes and edits.

Related: the WB save button uses the word "Edit" which isn't totally accurate. "Changes" is rather long, though, so not sure how you want to address it.

Webs101 wrote:I'm using v. 0.0.51 on Safari 6.0.2 in OS 10.8 and nothing I do can get the city field to update in the drop-down menu for highlighting. It's stuck on a single city, far from where I'd like to use it.

bgodette wrote:Specifically that's for the first alternate street. For the streetname that shows on the map and that is used for shield display by the client, it's .attributes.primaryStreetID. The segment's .attributes.streetIDs is an ordinal array for the alternate streets for that segment and can be empty.

Since JNF is being talked about out in the open, I'll be releasing it to the public once WME is updated. Making it work with the current public version isn't a real high priority when it's going to change significantly with the next release.

Including some of the short bookmarklets, that are popping up over in the champs forum, as buttons might be handy however.