7781Re: Partial success (printing now works, startup script doesn't)
- Apr 17, 2013--- In email@example.com, "ted_m_p_lee" <tmplee@...> wrote:
> More clues. With assistive devices enabled no error occurs when I run the startup applet (SS-WP). SS gets activated, but no SS window comes up. If I run the startup applet a second time, not having touched the SS icon in the dock, the SS window comes up and shortly thereafter gets repositioned. So I think there's something amiss in the script's attempting to wait until either SS starts or its window is created. I tried adding some delays or changing the delays in the script, but that didn't help. As I've said, I know essentially nothing about scripting, so I'll have to leave it in more capable hands to figure out.When you run SheepShaver itself, by double-clicking on the app icon, does the SS screen come up?
> As best I can tell, the main purposeof the startup script is to reposition the SS window to essentially full screen,
It just moves the window to cover up the space left by the now-disabled OSX menu bar. But the startup app will do much more in a forthcoming update, which I hope to release in a few days or a week.
> I replaced the printer folder action script from SS-WP 1.4.2 with the one from1.2.5 (which was working on the Mac Mini) and printing now works under Mountain Lion.
I'm sorry to say I no longer have a copy of 1.2.5. Could you send me that script? I'd like to track this down.
> OK -- Google is your friend. I did a search . . . The author of that showed a script that bracketed his window manipulation commands with a "try/end try" but I couldn't find any places to put that in the script that worked.Could you send me that link?
I'm sending you a copy of the new startup app, "SheepShaver-WP". It's a little bit cleaner and does more things. Could you try it? Please delete any and all copies of the Open WP Files app from your machine first.
- << Previous post in topic Next post in topic >>