#27081: mkvtoolnix: Can't get focus in mmg (the mkvtoolnix GUI) --------------------------------------+------------------------------------- Reporter: jds6p6h02@… | Owner: ruud@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.9.1 Keywords: | Port: mkvtoolnix --------------------------------------+------------------------------------- Comment(by ruud@…): Together with the developer I've found a solution to this problem. I'm currently in the process off creating a patch as a hot-fix. -- Ticket URL: <https://trac.macports.org/ticket/27081#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS

#27081: mkvtoolnix: Can't get focus in mmg (the mkvtoolnix GUI) --------------------------------------+------------------------------------- Reporter: jds6p6h02@… | Owner: ryandesign@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: 1.9.1 Keywords: haspatch | Port: mkvtoolnix --------------------------------------+------------------------------------- Changes (by ryandesign@…): * keywords: => haspatch * owner: ruud@… => ryandesign@… * status: new => assigned Comment: Replying to [comment:4 ruud@…]:

According to wxWidgets the preferred method is to create a bundle instead; what does MacPorts prefer?

I don't think I understand the question so I can't directly answer. I am not a Mac application developer so I don't know how these things are usually done by developers. If by "bundle" you mean a .app in the Applications folder which contains the executable and support files, then yes, that is the preferred method of delivering Mac OS X GUI programs, but many programs distributed through MacPorts have GUIs that are accessible via a binary in /opt/local/bin. In cases where that's how the developer provided the software, the MacPorts portfile will often choose to provide a wrapper application in /Applications/MacPorts to make it easier to launch. For an example of this, you can look at our currently first port alphabetically, 2Pong. The .app generally contains nothing more than a symlink to the executable in /opt/local/bin. I don't know whether doing this would be of any assistance to mmg. -- Ticket URL: <https://trac.macports.org/ticket/27081#comment:5> MacPorts <http://www.macports.org/> Ports system for Mac OS