A good idea. Ideally, a kind of designing frame with an object inspector (something that programming environments have, capable of generating code for objects created on a screen) would be useful. But this would work optimaly if Walter was structured as an Oriented Object Language with methods, etc., and it isn't the case. But maybe it's more easy to do for an enhanced element finder that would show the code used for a given control : the problem is how to manage the layouts that have different instructions for it.
Guess that would be a lot of work, though, and honestly, I don't have the skills to do so, as it would probably require a development in a compiled language (C++, Lazarus...).
Actually, what I would like first is a true debugger showing all the values used in a given rtconfig.txt, including the scalar ones : h, w, folderstate, folderdepth, trans_flags, etc., this, in real time. We have the SWS 'theme helper' but honestly it's not up to the job : I never use it...
__________________
DAW: Ryzen 3700X|Asus X-470Pro|32Gb|2 SSD512(M2)+1024|W10Pro(64)|RME Fireface UCX+ADA8200
Soft: Reaper|Cubase 10|Emulator X3 & several other VSTis (2 bridged)...
Gear: VMK-188+|MPD32|ME30P|Korg 05R/W|Roland D110|Yamaha TX802|Pre-MIDI stuff...
Last edited by cubic13; 09-08-2018 at 11:36 PM.
|