Using auto view rules to visualize anything with a function type as the resultant disassembly, by default.

You need to write a UI/UX book.

I’ve written blogs on UI programming. At some point I may heavily revise, extend, and polish them to become a book or something. But for now, here they are:

Is it already possible to watch std::vector?

In 0.9.15 and below, not generically. In the next release, auto view rules will receive support for generic type patterns, e.g. std::vector<?> -> ..., where ... is however you'd find the base pointer of the vector, and specify it as pointing to N elements. If C++ STL were sane, that'd be as simple as: std::vector<?> -> slice However, because it isn't sane, it may be more like: std::vector<?> -> wrap($expr._Mypair._Myval2), slice The other problem here is that the implementation is not standardized. So this rule will only work for one compiler, and there is no way currently to condition auto view rules by underlying toolchain. So, what will probably have to happen next is a mechanism to build auto view rules into the target executables themselves, and then conditionally doing that based on toolchain.

Pardon me if this feature already exists, but I’m using the RAD debugger right now, and I frequently view a data structure that is a union, and it would be *super* convenient if I could set which member I want to view by default for that particular type.

Do you mean a discriminated union, or a union used to name several members in different ways (e.g. a Vec4 with an x member, or an elements member)?

is this ide??? vim like or vscode??

Raddbg is only a debugger right? You don’t have a visualization for, say, callgrind profiles?

Correct

is it possible to use RAD debugger without a gpu ?