Michael Savich
2016-12-03 21:43:45 UTC
On another thread (https://sourceforge.net/p/audacity/mailman/message/35529999/ <https://sourceforge.net/p/audacity/mailman/message/35529999/>), I asked why we need to use the 10.6 SDK to build Audacity. The answer I got was that it is because Audacity still supports 10.6, which I take to mean that either the Audacity codebase or one of its dependencies needs that to use a deprecated/removed API, because as far as Iâm aware the 10.12 SDK can still build apps that will run on 10.6.
Iâve been looking to see if I can add support for the Touch Bar to Audacity, because I think itâd be a great fit. Iâve been experimenting with the wxWidgets source and I believe Iâve figured out how to bridge the gap between the c++ code and Cocoa APIs⊠of course, messing with the view hierarchy at run time is a little dangerous, but I wouldn't submit a pull request until Iâve figured out how to do this in a safe/maintainable way.
But, the one problem, the NSTouchBar API requires the 10.12.1 SDK⊠ðš Iâm not sure how to work around this. Is it possible to have communication between code compiled at two different API levels? Or is there another way to resolve this that Iâm not seeing?
Sent from my Mac
Iâve been looking to see if I can add support for the Touch Bar to Audacity, because I think itâd be a great fit. Iâve been experimenting with the wxWidgets source and I believe Iâve figured out how to bridge the gap between the c++ code and Cocoa APIs⊠of course, messing with the view hierarchy at run time is a little dangerous, but I wouldn't submit a pull request until Iâve figured out how to do this in a safe/maintainable way.
But, the one problem, the NSTouchBar API requires the 10.12.1 SDK⊠ðš Iâm not sure how to work around this. Is it possible to have communication between code compiled at two different API levels? Or is there another way to resolve this that Iâm not seeing?
Sent from my Mac