Thing with this is that you were originally talking about delay values within a note column, not line indexes
But yes, I know what you're referring to, and we are indeed missing a proper phrase-based equivalent of renoise.song().transport.edit_pos, which understandably hinders what tool devs can currently achieve. Adding such a property should of course be feasible... at some point in time. (Shout at danoise and taktik, not me, haha.)
Yeah, I did get Phrase Delay-writing (much like Pattern Delay-writing in PakettiR3) working, but then realized that there was no phrase_line_index I won't shout at you, I'll shout at taktik+danoise, but I'm sure they're busy with life, work, other things.
Would that really be so useful, though? I'd guess that you and I probably have fairly different view presets saved locally, based on our own common tasks and personal workflow needs.
If I switch from preset 1 to 2, but your tool doesn't know what my preset actually is, then what? I guess you could manually read each view property one by one — renoise.app().window.disk_browser_is_visible, renoise.app().window.active_middle_frame, renoise.app().window.pattern_matrix_is_visible, etc. — and then make some kind of educated guess about what I'm seeing, but that doesn't seem very ideal imho.
But for your own private use and finely tuned personal setup, sure... such a thing would still be useful, and doesn't really hurt anyone if it can be added.
I uhh.. Must admit that it's pretty much just a hope that maybe it'd be useful. Like having a specific View Preset that starts pattern-length sampling when triggered, and then returns to the pattern editor when sampling stops.. This kind of stuff. I just had a feeling that maybe it would actually be useful. Most of these ideas are fledglings until you flesh them out and make them into workflows. Before they're worked out, approved, logical and robust workflows, they need to kinda be bashed around until you get the goods out.
Yeah, the whole "launch function when view preset" only makes sense, if the scrip is allowed to destructively mangle view presets. or, if LUA scripts themselves have their own View Presets that are outside of the "Renoise basic 1-8 View Presets".
Actually, that'd be nice - you could leave the 8 View Presets well alone and instead "save Tool-Specific View Presets" and allow the user to open them, if they like.