workbench_window.py missing relative path in import

[SurfCityMojo]

Simple one... Method _editor_manager_default(), is missing relative path in import statement. Should be:

from .editor_manager import EditorManager

[rahulporuri]

Thanks for the report @SurfCityMojo . Can i ask how you came across this issue in the first place? Do you use workbench, directly or indirectly?

[rahulporuri]

#1034 should fix this issue.

[SurfCityMojo]

Hi Poruri, Yes, using workbench directly. My company has an internal app that was created 3-4 years ago using Python 2.7 and I'm in the process of updating it to Python 3 and more recent ETS package versions. I'm planning on taking a look at migrating it to the Task framework too because the initial layout is always wrong. I think there's a (known?) problem with restoring workbench-based layouts? Thank you for the fix! -Jeff

…

On Sun, Nov 7, 2021 at 8:59 PM Poruri Sai Rahul ***@***.***> wrote: #1034 <#1034> should fix this issue. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1033 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABCJHL77BLKKYGXU5QPPH5DUK5KM3ANCNFSM5HORVVNQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[rahulporuri]

I'm planning on taking a look at migrating it to the Task framework too

We highly recommend doing this as the workbench framework is deprecated and we might remove it in the future.

I think there's a (known?) problem with restoring workbench-based layouts?

I'm not sure. We don't use workbench actively internally so we're not sure what state the workbench framework is in. If you come across issues, please report them. We might not have the time to fix the issues, especially if they are non-trivial but we always welcome external contributions!