clipy / keyholder Goto Github PK

Create a keycombo validator that can be used in the standard.

• Shift + [A-Z] varidator
• Global hotkey varidator

Hey! I think you need to make a new release since the last on was made in 2020 and therefore it's package file points to some old dependency versions.

I would like to migrate my project to SPM, and this is the one project that has not yet added support for Swift Package Manager. Would be great if support for this could be added.

XCode reports that isMousePoint is now mouse

Hi guys!

I have installed KeyHolder via CocoaPods:

...
pod 'Magnet'
pod 'KeyHolder'

But there are some weird errors in Xcode:

What's especially confusing is this line:

What have I done wrong? :)

ps. is there an easy way to change components font size?

For some scenarios it would be nice to be able to record a shortcut for a key without the use of a modifier. This could be allowed by passing another parameter to the initializer which is then checked in the "validateModifiers" extension function, replacing
return KeyTransformer.carbonFlags(from: modifiers) != 0
...with...
return KeyTransformer.carbonFlags(from: modifiers) != 0 || isEmptyModiersAllowed

I can supply a pull-request if you think this is worthwhile.

Hi, I use YouTube in my Slidepad but every time I open Slidepad YouTube automatically starts playing if I left a Slidepad window on a YouTube video, even if my current Slidepad window isn't YouTube.

Is there any chance of disabling auto-playing a YouTube video? It seems difficult but it's also pretty annoying so it would be much appreciated!

When trying to checkout and build using Carthage, I get this error message

*** Building scheme "Magnet" in Magnet.xcworkspace
*** Building scheme "KeyHolder" in KeyHolder.xcworkspace
Build Failed
	Task failed with exit code 65:
	/usr/bin/xcrun xcodebuild -workspace ProjectName/Carthage/Checkouts/KeyHolder/KeyHolder.xcworkspace -scheme KeyHolder -configuration Release -derivedDataPath ~/Library/Caches/org.carthage.CarthageKit/DerivedData/KeyHolder/v2.0.1 ONLY_ACTIVE_ARCH=NO CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES clean build

This usually indicates that project itself failed to compile.

I also tried manually checking out and opening up in Xcode, like it says in the build instructions, but it says it can't find the library Magnet to include in RecordView, even though the Magnet framework is included in the project

Why is there no option to change the default search engine?

It doesn't make sense to show the clear* button when there's no keyboard shortcut set.

*

While the delegates give you a lot of power, it's also very verbose. Would be nice if it also provided a callback. I don't need most of the delegates. All I need is to know when the hotkey changes.

recordView.didChange { keyCombo in
	guard let keyCombo = keyCombo else {
		print("Key combo was cleared")
		return
	}

	print("Key combo changed")
}

The above would be an alternative to func recordViewDidClearShortcut and func recordView(_ recordView: RecordView, didChangeKeyCombo.

Hey 👋
Is it possible to enable fn + key support

Or at least does anyone know what fn will have modifier?
For example for option + key modifier would be 2048.

But what will it be in case of fn + key?

🙏

error… please ignore.

Probably going to fix this myself, but to track the problem until then, here's what I mean:

• click inside a RecordView: it obtains key view status and shows a focus ring
• enter any shortcut: it shows the shortcut and the modifiers properly
• try to enter another shortcut

I expected the shortcut to be overwritten, especially since the focus ring is still drawn.

But instead I hear NSBeep and the value remains the same until I click inside the view again.

The issue is in RecordView.endRecording():

 if window?.firstResponder == self && !canBecomeKeyView { window?.makeFirstResponder(nil) }

This properly emits an end editing event, but I think it should set the first responder back to self afterwards to remain consistent with the visual appearance (i.e. the focus ring that is still there).

It currently doesn't adapt well to dark mode:

This is how the system inputs look like in dark mode:

Hey! I've noticed that in dark mode it's hard to really see which characters are currently recorded. What do you think if we make "inactive" characters more transparent? I can contribute to that but would like to discuss the solution first :)