Status Update
Comments
am...@google.com <am...@google.com>
ot...@gmail.com <ot...@gmail.com> #2
Thank you for posting.
Kindly provide a sample app with screen recording and steps to reproduce for further checking.
[Deleted User] <[Deleted User]> #3
The issue is easily reproduced with the Stroke and Width settings for Buildings (3d and Footprint) within the latest Maps JavaScript API and both the old web-based Map Styles editor and the new cloud-based Map Styles editor. You can reproduce the issue by attempting to add an outline (stroke) of any width under Landscape-Human-made(man_made)-Buildings. The expected changes do not show in the rendered map within the Styles editor(s) or when loading the map via saved Map ID elsewhere.
I don't have time this week to author a screen recording that redacts my proprietary intellectual property, and I certainly won't be providing a copy of my software or authoring a sample app for you when you can already easily duplicate the bug in your own Map Styles editors.
I may have time to provide a marked-up screenshot from the Map Styles editor later tonight or tomorrow when I am back at my computer.
[Deleted User] <[Deleted User]> #4
To follow-up on this in an effort to assist you in bringing this bug to a resolution, please see the attached screenshot from the (old) Map Styles editor showing the issue and how you can duplicate it on your own. Similarly, the issue can also be duplicated in the (new) preview of the cloud-based Map Styles editor. Stroke color and width are not working as expected, for both the 3d and footprint style of buildings on the map. To assist you in locating the Map Styles editor, here is the link to Map Styles:
ma...@gmail.com <ma...@gmail.com> #5
Thank you for the information.
We have verified and logged this issue internally. Please note that we cannot give you any timelines, but you can star the issue to get notifications.
da...@loylap.com <da...@loylap.com> #6
am...@google.com <am...@google.com> #7
lo...@gmail.com <lo...@gmail.com> #9
ro...@gmail.com <ro...@gmail.com> #10
I did notice a recent change to the (new) cloud-based Map Styles editor which added the ability to edit the stroke color and width for the footprint style of buildings. That seems to be some positive progress.
ro...@gmail.com <ro...@gmail.com> #11
<codes><312220318></codes>
or...@gmail.com <or...@gmail.com> #12
ty...@gmail.com <ty...@gmail.com> #13
ty...@gmail.com <ty...@gmail.com> #14
Please add this to the list of bugs/issues that I have reported above: Building Fill color is missing the Transparency option.
ul...@gmail.com <ul...@gmail.com> #15
[Deleted User] <[Deleted User]> #16
Thank you for your message.
As per checking,
Our Engineering team is actively working on fixing the mentioned issues. We apologize for the delay and sincerely appreciate your understanding.
Rest assured that once we have receive any shareable updates, we'll let you know.
Thanks again.
ng...@gmail.com <ng...@gmail.com> #17
ra...@gmail.com <ra...@gmail.com> #18
There has been an update in our documentation related to the stroke color and weight. The following pages have been updated. In short "Stroke color and stroke weight customizations are not available for 3D style buildings."
-
-
Well, I guess that is one way to fix an annoying bug... just rewrite the documentation to make it look like the bug was intentional. I have to say, that is the funniest and most annoying thing I have heard in a long time. What a joke Google Maps API has become. If the goal is to force developers to seek alternative mapping solutions, you all are succeeding.
It is also worth mentioning, I am not privileged enough to actually have access rights to view either of the documentation links that were provided (internal to Google maybe?), but I will assume that they are just trying to cover up their mistake instead of actually fixing the issues. How utterly disappointing and frustrating!
ar...@gmail.com <ar...@gmail.com> #19
I assume they will update the doc to include fill/transparency on 3D buildings too
Description
"While BottomSheetBehavior captures the persistent bottom sheet case, this release also provides a BottomSheetDialog and BottomSheetDialogFragment to fill the modal bottom sheets use case. Simply replace AppCompatDialog or AppCompatDialogFragment with their bottom sheet equivalents to have your dialog styled as a bottom sheet."
So I changed my AppCompatDialog to BottomSheetDialog:
package my.package.ui.dialog;
import android.app.Activity;
import android.content.Context;
import android.os.Bundle;
import android.support.design.widget.BottomSheetDialog;
import my.package.R;
public class AccountActionsDialog extends BottomSheetDialog {
public AccountActionsDialog(Context context) {
super(context);
if (context instanceof Activity) {
setOwnerActivity((Activity) context);
}
}
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(getLayoutInflater().inflate(R.layout.dialog_account_actions, null));
}
}
Here is my layout file:
<?xml version="1.0" encoding="utf-8"?>
<LinearLayout xmlns:android="
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:orientation="vertical">
<TextView
android:layout_width="match_parent"
android:layout_height="wrap_content"
android:background="#ff0000"
android:padding="16dp"
android:text="Delete account"
android:textColor="#ffffff" />
</LinearLayout>
Then I use the following code in my Activity:
new AccountActionsDialog(this).show();
My screen becomes dimmed but the content of my dialog is not visible. It works fine when I use AppCompatDialog instead.
I've attached a sample project which demonstrates this behavior.
Device: Nexus 5X