Open marisademeglio opened 5 months ago
@rachanasinghg can you give me a recipe to reproduce this in the simplest way possible? E.g. no other jobs going on, and can you email me the source material used? The job log and settings.json file would also be useful to see (settings.json is in C:\Users\<username>\AppData\Roaming\pipeline-ui\settings.json
). Email me the files or if you post anything here, make sure to remove sensitive info e.g. TTS API keys.
Hi Marisa,
Have mailed you the steps and files as requested. Thanks.
Regards Rachana
The issue here is that the user did not expect "Edit job" to create a new tab but to edit the job in an existing tab. But this behavior is intentional and was requested by #130. We may however consider making a note on the "Edit job" button or in the documentation that it will create a new tab.
@rachanasinghg @marisademeglio note that the original behaviour (edit in place instead of in a new tab) is still possible : We added an "Editing jobs in new tabs" setting to control this in the Settings window under the "Behavior" section.
Thanks @NPavie , it works now. Nice to know about this checkbox. One more suggestion, it will be good not to open multiple tabs as per Edit job button clicks, 1 or 2 tabs are still ok, so many will surely create confusion. Also, if 2 duplicate tabs are created then they should be side by side, in the first image which i shared named Duplicate job Created, the first job duplicate is created at 6th job position (when user presses the Edit button). It will be great if that can be handled. Thank you.
Testing feedback from @rachanasinghg for 1.4.0-beta