View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0001440||NoesisGUI||C++ SDK||public||2019-04-02 15:21||2019-08-08 17:56|
|Target Version||Fixed in Version|
|Summary||0001440: EASTL Version|
|Description||Hi guys, is there any plans to update the EASTL version to the official Github repository. It looks like version 2.0 is being used from the old unofficial source code which came from the original ZIP released in 2010, the newer 3.0 version is now completely open source officially maintained by EA now: https://github.com/electronicarts/EASTL|
Only reason I'm asking is I tried to use the Visual Studio debug visualisers (https://github.com/electronicarts/EASTL/blob/master/doc/EASTL.natvis), but they're written to work with 3.0 and don't work correctly with the types so it's making debugging the internal types a bit more tricky than it should be.
|Tags||No tags attached.|
Yes, we have plans for this. We are going to deprecate EASTL in favor of our custom containers. EASTL is huge for us, we want something smaller to improve compiling times and performance. And yes, we will provide a natvis configuration for this new implementation.
This is something we are already working on. Thanks for the feedback!
|Just an update about this. The branch without EASTL, with new containers, with proper .natvis and huge memory improvements is almost ready to be integrated into trunk.|
That sounds awesome, good work.
One additional thing that might be worthwhile going in the .natvis is the ability to see the DependencyProperty values for a DependencyObject. Quite often in the debugger I want to output the values of the dependencyproperties. I have to keep writing getters and logging out the values. In managed C# I can just hover over the objects and the getters work great in the debugger. I don't know the best way to simulate it but it would be a massive help whilst debugging in C++.
Is it worth me opening a new ticket for this feature request?
Yes, please open a new ticket for that. We were thinking about that, we need custom native visualizers because we need to execute code to evaluate DependencyProperties.
|2019-04-02 15:21||steveh||New Issue|
|2019-04-05 12:01||sfernandez||Assigned To||=> jsantos|
|2019-04-05 12:01||sfernandez||Status||new => assigned|
|2019-04-05 21:21||jsantos||Note Added: 0005601|
|2019-08-08 17:23||jsantos||Note Added: 0005918|
|2019-08-08 17:41||steveh||Note Added: 0005919|
|2019-08-08 17:56||jsantos||Note Added: 0005920|
|2019-08-08 17:56||jsantos||Note Edited: 0005920||View Revisions|