Latest Contributions by TroyFoster

1.) Will any version of ArcGIS Runtime 100.x work with 6.5.2? ( I'm having a hard time finding the old system requirements) https://developers.arcgis.com/qt/v100/reference/system-requirements/ It did take me a little digging to find the old requirements.  As I undertstand it, the switch from Qt5 to Qt6 was a large part of the reasoning for the 100 to 200 change. 2.) Will I have a hard time moving my current code using 100.13 to 200.3?  I've already seen all the compile errors and wondering if it is possible with some code adjustment or is it really a gruesome process. Looking back at my notes from my changeover from 100 to 200, the big things for us were: using qmake6 instead of qmake Esri changed their includes in their headers so that they forward declare everything they can and then force your user classes to include pieces individually used.  Or there is a single include compatability header that includes everything they have. Esri removed/updated some functions they had marked as deprecated for quite a while, like on the Error class they changed int error.code() to be [some enum] error.errorType() Converting a geometry to an envelope, you need to explicitly call .extent and not use the implicit conversion function Esri made some Geometry base class copy constructors explicit.  They provided geometry_cast functions that does some checking on the type of the geometry. Qt5 to Qt6 had some changes for how some of their classes behaved, like in QMouseEvent and the parent classes for that. I'll just give one example. Runtime::VerticalAlignment had 6 parameters in 100.13 but 200.3 calls for two, etc Where is VerticalAlignment in the documentation?  I see a function for setting that on TextSymbol and an enum named that, but those match up in both 100 and 200.  Or am I looking at c++ documentation and you are looking at Qml or something like that? ... View more

would intersection work? ... View more