Ask Your Question
2

Double-clicking a file from finder doesn't open it in Wing when the editor is already active

asked 2019-12-20 07:49:28 -0600

jrobijns gravatar image

updated 2020-05-25 08:27:03 -0600

Using macOS Catalina and Wing Pro, I have the following issue:

When Wing is NOT active and I double-click a .py file somewhere, Wing starts and opens that file.

Whenever Wing is already active, double-clicking a .py file does switch to the Wing window (changes focus to it), but it does not open the file. So any subsequent source files, I have to open from the file menu in Wing. It doesn't matter how many files I have open in Wing at that time (even with all files closed it doesn't work).

Completely removed Wing and all settings files, re-installed and tried again. No joy. This one is pretty recent and I have to say... not a fan.

edit retag flag offensive close merge delete

Comments

I suspect this is Catalina breakage. What version of Wing do you have?

Wingware Support gravatar imageWingware Support ( 2019-12-20 08:25:23 -0600 )edit
1

I'm experiencing the same thing. Everything was working great but then I got a new MacBook and migrated my files to it. The new MacBook is running Catalina, and I made sure to uninstall and then reinstall the very latest version of WIng IDE 101 7.1.3.0. If Wing is not currently running, then double clicking on a Python file will start up Wing and open the file. But then if I double click on a second file the Wing app comes to the foreground of the desktop, but the file doesn't open!

ProfAB gravatar imageProfAB ( 2019-12-22 18:54:55 -0600 )edit
1

I am also having this issue, is there any possible fix beyond "Catalina Breakage"? I'm using version 5.1.12-1

Catalina also broke my anaconda install, and now Wing also can't select the correct python app for a custom python executable

cheikes gravatar imagecheikes ( 2020-04-23 15:07:28 -0600 )edit

I think a broken Anaconda caused by installing Catalina can be fixed by removing Anaconda and installing it again. Unfortunately we still don't have a fix for the Catalina file opening issue. The problems with .app packaging on Catalina are definitely quite odd. I keep hoping Apple will fix it since we have not found a work-around, but it's probably something very specific to perhaps shipping a Qt app or something like that. The other issues we were able to solve required bizarre solutions like hiding certain files in a .zip, apparently to "outsmart" Gatekeeper. We will continue to try to solve this, however, although any fix would only be in Wing 7. Sorry about this!

Wingware Support gravatar imageWingware Support ( 2020-04-24 08:54:28 -0600 )edit
1

For my workflow, this really is very annoying. If it's not something you can fix, I can respect that. But boy, this is annoying.

jrobijns gravatar imagejrobijns ( 2020-04-29 09:52:55 -0600 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2020-05-25 08:26:48 -0600

updated 2020-05-25 08:28:40 -0600

This should be fixed in our next release, which will rework how Wing starts in order to avoid the problem. The issue was that Wing's startup script was a shell script and Catalina didn't like that for some reason while it did work with previous macOS versions. The fix will require re-downloading Wing rather than just using Check for Updates since it makes changes in the overall application framework.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

3 followers

Stats

Asked: 2019-12-20 07:49:28 -0600

Seen: 740 times

Last updated: May 25