Attached is a small MMPK, created in Pro 2.0, that demonstrates a bad symbol rotation in Runtime 100.1 [I don't recall seeing this issue in Pro 1.4.1/Runtime 100.0, but I may be wrong].
Here's how it appears imported into Pro:
And here's how it appears in Runtime:
Thanks, Mark. I'm able to reproduce the issue in v100.1 and it looks like it did not render at all in v100.
Also, I find that when you opt-out advanced symbology, it renders just at it would in ArcGIS Pro. Do you mind trying the following workaround?
<SPAN class="keyword token">var</SPAN> mmpk <SPAN class="operator token">=</SPAN> <SPAN class="keyword token">await</SPAN> MobileMapPackage<SPAN class="punctuation token">.</SPAN><SPAN class="token function">OpenAsync</SPAN><SPAN class="punctuation token">(</SPAN>path<SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">;</SPAN> <SPAN class="keyword token">var</SPAN> map <SPAN class="operator token">=</SPAN> mmpk<SPAN class="punctuation token">.</SPAN>Maps<SPAN class="punctuation token">.</SPAN><SPAN class="token function">FirstOrDefault</SPAN><SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">;</SPAN> <SPAN class="keyword token">foreach</SPAN><SPAN class="punctuation token">(</SPAN><SPAN class="keyword token">var</SPAN> layer <SPAN class="keyword token">in</SPAN> map<SPAN class="punctuation token">.</SPAN>OperationalLayers<SPAN class="punctuation token">.</SPAN>OfType<SPAN class="operator token"><</SPAN>FeatureLayer<SPAN class="operator token">></SPAN><SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">)</SPAN> <SPAN class="punctuation token">{</SPAN> <SPAN class="keyword token">var</SPAN> table <SPAN class="operator token">=</SPAN> <SPAN class="punctuation token">(</SPAN>ArcGISFeatureTable<SPAN class="punctuation token">)</SPAN>layer<SPAN class="punctuation token">.</SPAN>FeatureTable<SPAN class="punctuation token">;</SPAN> table<SPAN class="punctuation token">.</SPAN>UseAdvancedSymbology <SPAN class="operator token">=</SPAN> <SPAN class="keyword token">false</SPAN><SPAN class="punctuation token">;</SPAN> <SPAN class="punctuation token">}</SPAN> MyMapView<SPAN class="punctuation token">.</SPAN>Map <SPAN class="operator token">=</SPAN> map<SPAN class="punctuation token">;</SPAN><SPAN class="line-numbers-rows"><SPAN></SPAN><SPAN></SPAN><SPAN></SPAN><SPAN></SPAN><SPAN></SPAN><SPAN></SPAN><SPAN></SPAN><SPAN></SPAN></SPAN>
I have logged the issue so our team can investigate further.
Thanks.
Jennifer
I took a quick look, and symbols look good without the workaround. Thanks!
I've been busy on other projects, but I hope to check out all of my reported issues this month.
Hello Mark,
Just following up on your original issue in this post regarding Symbol Rotation not getting honored. This has been fixed in 100.7. Did you get a chance to try it out and remove any existing workarounds? The symbol rotation should be honored without any workarounds.
Please note, other issue in this post that you reported regarding cloning layer renderer stripping out definition expression and other properties still exists in 100.7.
Thanks,
Preeti
We are currently working on solidifying the symbols with visual variables. I am hopeful issues like these will get resolved as part of that work. Sorry about the inconvenience.
I tested with your test data that workaround to use simple symbols continues to work with 100.6.
Also feel free to let us know if you have other test cases for symbology that aren't working correctly.
The problem is still present in 100.6. That's just plain pathetic!
Looks like this problem has resurfaced in 100.5. The old 100.1 workaround fixes it.
Hi,
The original issue should now be resolved in the recent v100.2 release.
Please download the latest Visual Studio extension from ArcGIS for Developers or update your NuGet packages via the NuGet package manager.
Cheers
Mike
Unfortunately, I can't change the UseAdvancedSymbology setting once the table is loaded. I tried cloning the layers, closing the GDB, even opening the MMPK a second time, but in those cases I couldn't get the map to load.
Hi Mark, I'm not aware a way to that without loading the metadata for the table since the layer doesn't have any information about it's content before that is done. If you are using MMPKs the loading operation shouldn't be too expensive since no network calls are done at that point.
Is there any way to determine the geometry of a feature layer without loading the table? I would like to be able to apply the workaround only to point layers (I have polyline layers with advanced symbology).
No problem, I updated the workaround a bit - no need to load and clone.
That works for me. Thanks!
Les membres connectés peuvent publier, suivre les mises à jour, et plus encore. Nouveau ici ? Inscrivez-vous gratuitement.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
