Quote:
Originally Posted by Dragokas
Or better, if you could make it support relative paths, like:
|
I think its better when i add a propper Pre/Post-build events that you can edit in the configs and scrap the "Shell". Otherwise its getting pretty confusing. The BasicPawn CompileSource function is already pretty bloated.
Quote:
Originally Posted by Dragokas
I also tried to use there "%inputfolder%" as pre-defined macro for your "Shell", but it doesn't accept it.
|
-
%inputfilename%/
%inputfolder% - Only works when the tab file is valid (on disk).
-
%includes%/
%compiler%/
%output% - Only work when the include/compiler/output paths are set manualy.
"Shell" is pretty old and flawed, better dont use it. Ill replace it with Pre/Post-build events in the future.
Quote:
Originally Posted by Dragokas
"MS Visual Studio" F12 shortcut for "Go to definition"
|
BasicPawn isnt much context aware to determind what is where located. Thats why i put "List references" instead.
However, i could add shortcuts for "List references" and make the information tab accept keyboard inputs too.
Quote:
Originally Posted by Dragokas
I don't quite understand how to use autocomplete feature.
|
Its not much different. You just have to hold "Ctrl" now.
To display all available shortcuts
Go: Help > Special Controls
Quote:
Originally Posted by Dragokas
why I can't setup paths via "Default" config name.
|
The "Default" config is read-only. Its cant be modified. Its mostly used for working out-of-the-box.
__________________