I get the idea that these bugs are related to the structure of the objects sent from the QGIS and ArcGIS connectors, and have something to do with collections, SpeckleMaterials and displayStyles, but I’d need a bit of help to get started on fixing these bugs and contributing.
@Kateryna These bugs are all part of QA on the next gen ArcGIS connector for the coordination workflow: let’s fix them internally to make sure colors and collections are handled properly
@JoostGevaert We’re no longer using displayStyle in next gen connectors: instead we are handling renderMaterial and color as proxies. Unfortunately we don’t have docs up for proxies yet for me to point you towards, but I’m happy to do a quick call with you to explain the structure if you’re looking to contribute!
My 2 cents for non-nextGen connectors: QGIS → Viewer issue with non-selectable features in the viewer is due to the old version of QGIS connector it was sent from: it is solved in 2.20.1-alpha and following versions
QGIS → Rhino (v2 & NextGen) and ArcGIS NextGen → Rhino v2 are not the target workflows, the goal is to clean up outdated features in nexGen (which means some of the features sent from v2 connectors will not be supported, and vice versa)
Finally, v2 to v2 (QGIS to Rhino) colors issue from here I will check again