search

BCLibCoop / nnels-a11y-publishing

GNU Lesser General Public License v3.0
5 stars 0 forks source link

DropToScript does not work on Mac OS X #16

Closed zwettemaan closed 5 years ago

zwettemaan commented 5 years ago

This might be related to the Mac OS X version. Farrah is using 10.11.x (El Capitan).

zwettemaan commented 5 years ago

@flittle8 I had another thought. What is the setting of your Security & Privacy control panel?

Go to System Preferences, click Security & Privacy. What does it say for 'Allow apps...'? It should say App Store and identified developers'. If not, you need to click the lock and change it...

Screen Shot 2019-05-03 at 6 55 59 PM
flittle8 commented 5 years ago

@zwettemaan Yes, those are my settings: "App Store and identified developers"

zwettemaan commented 5 years ago

@flittle8 I managed to set up Mac OS X El Capitan, and tried it out, and it all works. Grm.

Would you be willing to do a screenshare some time next week. I'd want to take control over your system and poke and prod a bit to get an idea of what is going on.

flittle8 commented 5 years ago

@zwettemaan Sure let’s do it. When works for you? I’m currently in the UK time zone.

zwettemaan commented 5 years ago

I'll send you a Doodle (scheduling) invite. It'll be late evening for me, early morning for you.

zwettemaan commented 5 years ago

Ok, we figured it out. DropToScript was accidentally configured with a default script. If and when that happens, dropping an item onto DropToScript will auto-select that script and provide no UI.

So the DropToScript was working, but because a default script was selected, no feedback was given.

Morale: I'll add some more feedback to the DropToScript and make it show a report of how many, if any, files it processed. That way the user can tell whether the program really did not work vs silently went to do its business.