What does the highlighted mean?
-
QtCreator does not know how to evaluate the function calls???
Screenshot -
And my next question is going to me how is this automatically resized inspector area is considered useful???
another screenshot
Is this some sort of sophisticated bullying? -
Oh, wasn't that meant to be funny?
-
Qt Creator routinely fails to present even the local variables on Linux and OS X. Deal with it. Use
qDebug()
. -
@nulluse said:
QtCreator does not know how to evaluate the function calls???
No. QtCreator is not a debugger. The debuggers certainly can, but apparently just not that one. This happens. Take your beef with your debugger vendor.
First of all there's no functionString::number(quint32)
. All staticnumber
functions take two params. Debuggers don't usually know about default parameters. I tried it with windows debugger but it has problems with that (no matter if called from VS, CDB command line, QtCreator or WinDbg). It's possible that some optimizations are to blame as it works in certain contexts but not others (even with inlining disabled). If you need it often you can define a wrapper function for this in your own app (dead code will be gone in release mode anyway):QString foo(quint32 bar) { return QString::number(bar); }
At least my tests allowed me to call this successfully from the evaluator.
Is this some sort of sophisticated bullying?
I don't think so, no. The columns expand/collapse when you click on the empty space below. This feature is actually really useful when working with long expressions or long expression results (e.g. a cast to a function pointer taking couple of std container pointers really burns through your character count). Toggling in and out to see the whole expression or the value with one click is a time saver compared to adjusting via header handle.