mirror of
https://github.com/keycastr/keycastr.git
synced 2026-05-15 14:15:50 -06:00
[GH-ISSUE #62] Single-character visualizer #49
Labels
No labels
bug
compatibility
discussion
documentation
enhancement
help wanted
help wanted
investigation needed
pull-request
release
visualizer
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: github-starred/keycastr#49
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @SketchySwift on GitHub (May 9, 2016).
Original GitHub issue: https://github.com/keycastr/keycastr/issues/62
When I go from one desktop screen to the other, keycastr only works n the first screen. Also, why does keycastr show everything into one sentence. Could you please make it like mousepose? The text be's in the center and it shows one key by one key. http://quick.as/jbv3tm5vr Here is an example. You see how it becomes so long? it would be nice if it showed the key one by one like this: http://quick.as/62wkuy4gy it shows it like one by one(each press).
@sdeken commented on GitHub (Sep 21, 2016):
I think there are two different issues discussed here. The first is that it doesn't cross desktops, and we'll have to do something about that. The second is that the default visualizer can get pretty long, but the Svelte visualizer doesn't have a similar issue. Does the Svelte visualizer work better for what you want to do?
@akitchen commented on GitHub (Sep 21, 2016):
I don't understand the issue about "crossing desktops"
With multiple displays attached I can put the bezel anywhere I want
When using multiple "Desktops" (Apple called them Spaces at one point) KeyCastr works fine in any/all of them.
Could we get more specifics on what you're hoping to see from the app regarding multiple desktops?
Regarding the other issue, you could try adjusting the "keystroke delay" or "linger time" options in the default visualizer to achieve the result you're looking for
@SketchySwift commented on GitHub (Sep 22, 2016):
Problem 1) so basically, if I am typing on Desktop screen 1, it will show the strokes as normal but when I switch to second desktop screen, i don't see the strokes/text on this screen, rather when I switch back to desktop 1, I see it there
Problem 2) Well almost what I had been hoping for, but the text isn't in the center, maybe giving an option to the user about where the text should be displayed would be nice!
@sdeken commented on GitHub (Sep 22, 2016):
Problem 1 we're covering under #64. The second problem I think we can cover with an additional visualizer that shows just one key at a time, which would make for a fun side project.