You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You see 1 warning, but you're unable to double click it instanlty and move to a specific line of code.
That requires you to scroll mouse a little bit firstly, to found such line:
What I suggest:
Parse that output, and after all output is displayed in "Information" window, complement it with only such 3 lines:
Summary:
[05.08.2021 19:19:04] H:\_To_games\Left4Dead_2\My_mods\Weapon\WeaponSets\scripting\l4d_weapon_set.sp(1070) : warning 204: symbol is assigned a value that is never used: "type"
[05.08.2021 19:19:04] 1 Warning.
And so on for "errors".
So, these most important lines will always be the last in window, and you can double-click them instantly after compilation attempt even if "Information" window size is minimal.
And, yeah, I can always change a size of "Information" window to see all required lines instantly. But, this is a waste of work space.
The text was updated successfully, but these errors were encountered:
dragokas
changed the title
Console output parsing & repeating most important parts
Make a "Summary" addition in "Information" window with frequently used info
Aug 9, 2021
This is for convenience only.
You see 1 warning, but you're unable to double click it instanlty and move to a specific line of code.
That requires you to scroll mouse a little bit firstly, to found such line:
What I suggest:
Parse that output, and after all output is displayed in "Information" window, complement it with only such 3 lines:
And so on for "errors".
So, these most important lines will always be the last in window, and you can double-click them instantly after compilation attempt even if "Information" window size is minimal.
And, yeah, I can always change a size of "Information" window to see all required lines instantly. But, this is a waste of work space.
The text was updated successfully, but these errors were encountered: