64-bit version?

[dtenenba]

Any plans to build a 64-bit version? macOS is going to drop support for 32-bit binaries at some point and is starting to show warnings about 32-bit apps including Jumpcut.

The current release appears to be 32-bit:

$ unzip Jumpcut.app.zip
$ cd Jumpcut.app/Contents/MacOS
$ file Jumpcut
Jumpcut: Mach-O executable i386

Thanks

[rsre]

I tried to build it for x86_64 with Xcode 10.1 on macOS 10.14.1 but it throws more than 100 warnings and then the linker fails. I'm not sure if it's worth spending the time to update it.

[saagarjha]

I haven't actually touched Jumpcut for a while, and it's now partially broken anyways. I'm not sure it's worth trying to keep the old codebase compiling for newer versions of macOS; I am considering rewriting it at some point so that it's reasonably similar to the original but using modern Cocoa.

[edreggi]

10.14 Mojave is asking for an update of Jumpcut. Any thoughts on updating the code?

I absolutely live by this software and would donate. Thanks!

Ed

[dtenenba]

I recently discovered flycut which is based on jumpcut and seems mojave-compatible.

[snark]

@dtenenba , @edreggi , and anyone discovering this issue via search, the original Jumpcut is now 64-bit and Mojave-compatible: https://snark.github.io/jumpcut

[snark]

I'd in fact be very interested in seeing how a rewrite in Swift would look, @saagarjha -- I'm not sure that the payoff would be that much initially, but it would definitely make it more futureproof. I don't really have the time to do it myself at the moment (maybe someday!) and now that Jumpcut is 64-bit it can probably keep going for several more years.

[saagarjha]

Ooh, nice! I should probably update the description on this to be "my personal changes to Jumpcut" then and go take a peek at bad my Objective-C skills were three years ago so I can just create a patch out of it and apply it on top of your code here. Maybe if I get time at some point I'll try my hand at converting parts of it to Swift :)