| Register | FAQ | Calendar | Search | Today's Posts | Mark Forums Read |
|
#11
| |||
| |||
| On Aug 25, 3:31 pm, Jeff Hobbs <jeff.ho...@gmail.com> wrote: > On Aug 25, 12:18 pm, blomc...@gmail.com wrote: > > > But I have to say, all of this is quite an effort to go to to simply > > get a tcl application to appear in the foreground when launched, which > > is expected behavior for any app on any platform that is not > > specifically launched as a background process. I don't understand why > > tcl/tk apps on the mac don't do this automatically. I suppose this is > > an issue with the aqua/tk system, so perhaps I'll ask around there. > > What you think is not what is true. This is an intentional behavior > on OS X by the OS itself and effects more than Tcl/Tk. Read up on why > in the archives here or the tcl-mac mailing list. > > Jeff Thanks for all responses. Yes, I realized yesterday that I was mistaken about apps foregrounding by default; I am fairly new to the mac, and typically launch stuff using the "open" command (eg open -a xcode somefile), which does cause the app to go to foreground. So now where I used to have the main tcl script that was callable on win32/osx/linux as "myapp.tcl" from anywhere (assuming location in path) I now have a "myapp.osx" which is a one-line script that says "open -a myapp" where myapp.app is the new application bundle. thanks all -thomas blom |
![]() |
| Thread Tools | |
| Display Modes | |
In an effort to better serve ads to our visitors, cookies are used on objectmix.com. For more information, check out our Privacy Policy.