First of all, it would be an editor bug.
The debugger (any of them) only delivers the content of the window (as text), but nothing else.
The yellow hint is created using IpTurboProDsg package => so if uninstalled, the grey hint is used. Yet, then all hints would be grey.
Probably not applying to your case either (as it looks like the source editor has focus / the very editor to which the hint belongs). On Windows, if you have more than one screen, and they have different DPI settings, and a window on one screen is focused, but the mouse hovers over a window on another screen, the wrong dpi is used to calculate the hint offset. => Btw, such DPI mixes even affect apps like the windows explorer, to have incorrect display in some cases...)
As for the position, I have no idea, but maybe it is a side effect of the below (if the below applies....)
The yellow hint is a html hint. I am not aware of any issue like the following, but it would not be impossible.... The content of the hint, might be such that it breaks the processing into html. If such breakage could happen (which I don't know), then I don't know if there would be a fallback to the grey hint....
For starters the "&" may have suddenly meaning or side effect...
Actually, after typing the above, I just made the test.
program Project1;
var
&a:integer;
begin
&a := 123;
a := 123
end.
Hovering the "a" is fine. but the "&a" is not.
Further this may even be a codetool bug => explaining why the hint has no other content (e.g. no position of declaration).
In the above code example, while NOT debugging, I can hover the "a" and get some info, but not on the "&a" (neither of the two).
And the same goes for ctrl click jump attempts.
So, at this time, I say this is primarily a codetools bug, but there may be additional issues in the hint handling code...
Recent
