At any session change, including initial startup - we first load session and then call load_all_temp_files_idle() which (re)loads all temp files and changes active tab to last loaded temp file. I added a workaround to re-activate originally active tab by re-opening it (i guess no other way to do it)
Ah, right, I overlooked it - I thought it only removed the API call.
i could try, but this would anyway be used only when we try to close temp file tab and chose save-as. But when user just tries to save-as temp file using menu - it will still be opening on temp folder
OK, I didn't think of this possibility - I guess it doesn't make sense to spend time on this then.
lol you're right, changed logic to this one
Better ;-)
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.