Last Block selection memory for audio timing

[Jeroi]

Now that harukolover has made a batch for audio commit and text commit for multiple lines, Aegisub anymore is missing "Last block selection memory" which is used always when new block of lines are timed and moved to next line.

Process:

1. Next line on commit needs to get block selection and save it in memory or global table or class or txt file.
2. Then block memory reports == true, then "Next line on commit" needs to check if it is true, then check if next line is in Block selection memory and if it is == jump that line over and check next..
3. Next line on commit have to check also, if next line is higher than highest line number in selection block memory then if it is, cleas block selection memory.
4. If it is highest, clear block selection memory and it reports now == false
5. On mouse line aktivation, clear block selection memory always if block memory reports = true

ADDITIONAL INFORMATION:
This feature would make this happen:

1. Aktivate 1-3 and 5-6 and commit timings
2. Aktivate line 4 and commit timings
3. Aktivate line 7

[nielsm]

You're missing one thing: What's the point of this.
It makes no sense as you're describing it. (I can't understand what's supposed to happen and what the purported use cases are.)

[Jeroi]

So when timing subs, you need aegisub to handle block selection the way haruka lover fixed it is now like this:

1. Select 1-3 and 5-7
2. Commit timings
3. Line 4 is activated

But, when you commit timing to line 4 this happens:

4. Commit timings
5. Line 5 is activated

So now you need manually again to move aktivation to line 8

Then we come to my suggestion that block slection memory would remember the timed lines of last block of selection. Ie. Aegisub would make table of: last_block = 1,2,3,5,6,7
Now if aegisub have this memory, lets get back to number 4:

4. Commit timings
5. Line 8 is aktivated

This is mostly needed for fast timing, aegisub would support automatic line swithcing making timing a lot of easier, even if you time many lines in same time, aegisub knows all the time witch lines are not timed yet.

Even better feature would be adding aegisub timing mode, where aegisub remembers time changes from default times, so even tho you switch to any already timed line with mouse, aegisub would then move to next untimed line.

Ie, when you move to next not timed line, make audio default selction start from last already timed line's end time.

[Harukalover]

Remembering what lines were modified and then moving to the next line that was never modified on commit, would likely just confuse a lot of people. If it ever does get implemented I believe it should be an optional setting.

[TheFluff]

Rejected, closing.