foxitrot wrote:In the past, there were already proposals, how to reshape the display area, especially this thick block. I do not remember anyone from Waze ever responding to them
IMHO, something as important as the client GUI should be worth even its own subforum, for proposals, problems, etc. Surely Waze has their own opinion on the client's look and feel.
I don't see it mentioned in this thread if I search , but it will switch only if Waze is started within 30 minutes of sunrise or sunset. It was acknowledged in the beta threads and Perlin did say it will be discussed with the developers for possible change in an upcoming version.
As asked, could you verify if the recent change for daylight savings in most countries affected this, or is the 30 minutes still valid?
davipt wrote:I've noticed now a regression on the official client (can't test right now the beta, it's on the "old" iPhone at home):
- Select a segment on the map.
- click more->set as start point
- pick up another point as destination (for example, from the favorites, like work)
1. pick "go". everything is ok
2. pick "routes", click on the any route, everything is ok
3. pick "routes", click on map, click ok (or pick a route, doesn't matter). The route on the map is now a route from where I am to the destination, not the choosen start point.
The crucial point here is to open the map view of the alternative routes. Not opening the map works as intended
StunGod wrote:I've done some searching, but haven't been able to find anything recent on this: is there any plan to reduce the amount of screen real estate the directions block takes up on the screen? We lose about 1/3 of the useful screen space in landscape mode, all the time. It's useful when approaching a turn or the destination, but absolutely useless to take all that space when my next turn is 5, 10, 20, 100 miles away. Any way to toggle it so it only shows up when necessary?
StunGod wrote:I agree. The UI for an app like this is one of the most important pieces. And this is a pretty big thing to ignore, considering it's probably not too hard to fix.
Users browsing this forum: AleLenziBR, Baidu [Spider], Google Feedfetcher