Latest Contributions by JamesBallard1

@JustinSteventon thanks for letting us know it's something you are interested in. We value this type of feedback and I will pass it along internally. ... View more

@imbachb thanks for the detailed report. I can reproduce what you're seeing. We are incorrectly allocating a new part every time this is called for some internal reasons related to how we cache collections. m_polyLineBuilder->parts()->part(0)   As soon as the parent goes away, it all goes away but that's not very helpful since parents are typically long-lived. Here's some test code I whipped up, along with a temporary workaround for the meantime. qDebug() << "Test started"; auto* m_polyLineBuilder = new PolylineBuilder(SpatialReference::webMercator(), this); m_polyLineBuilder->addPoint(0, 0); m_polyLineBuilder->addPoint(1, 1); m_polyLineBuilder->addPoint(2, 2); qDebug() << QString("PolylineBuilder part count: %1").arg(m_polyLineBuilder->parts()->size()); for (int i = 0; i < 10'000'000; i++) { if (i % 1'000'000 == 0) { qDebug() << QString("i: %1").arg(i); } auto* partCollection = m_polyLineBuilder->parts(); //auto* part = partCollection->part(0); std::unique_ptr<Part> part {partCollection->part(0)}; // workaround } qDebug() << "Test finished";   Deleting the part shouldn't alter the contents. It will be recreated (as you found) on the next call. I'll get an internal bug logged so we can see about addressing this in an upcoming release. Thank you for letting us know about this. ... View more

Ok @JustinSteventon, sounds good. If you were still having issues with Qt 6.8.0, that is something I'd like to chase down. You should be able to use 6.8.0 if you want, and that's the latest LTS release as well. ... View more

Hi @ArmandoGarcia3 . @TroyFoster is spot on with point 2, and the "incomplete type" errors you're seeing are related to our product following c++ best practices and forward declaring everything possible. You can either include all those headers in your project, or we provided an "ArcGISIncludeCompatibility.h" header for situations like this which brings in everything. We don't recommend using that header as it will negatively impact your compile times, but it should get you beyond those errors quickly.     ... View more

Hi @HunterMorganBell. Thanks for reaching out with this info. Unfortunately this is an ABI break in the Qt framework itself. We noted this in our previous release notes here: https://developers.arcgis.com/qt/release-notes/prior-releases/release-notes-for-200-3/#known-issues To address this in our upcoming release we are moving up our builds to use Qt 6.5.6 minimum which addressed the issue. In the meantime, hopefully you are able to use 6.5.5 for your development. Apologies for this, but it should be sorted out with our 200.5 release, which should available in a few months. ... View more

Ok based on those messages, there could be two different issues. First, our Maps SDK for Qt requires the positioning, sensors, and websockets Qt modules. Double check that those are present when you installed Qt. Those are typically listed as additional liraries   As for the strange "no such file" problem, that could be a Windows-specific problem we run into on the team ourselves. That (any related problems) happen with very long paths. One way that we deal with that is to drastically shorten the shadow build folder path. Here's an example on my machine. In the projects tab, I changed the "Build directory" to a shorter length than the default. ... View more