Skip to content

[Bug]: History stacking shifts overlay vertically with custom anchor #72

Description

@esphynox

Keyty version

Observed in the first release that included custom anchor positioning, reported on August 3, 2026 in the follow-up to #57.

macOS version

Not yet provided.

Install method

Other

Steps to reproduce

  1. Open Keyty and enable history so multiple keystrokes remain visible.
  2. Choose a preset anchor that demonstrates stable vertical stacking, such as top center or bottom center.
  3. Switch to Custom anchor and place the overlay near the top or bottom of the screen.
  4. Generate enough keystrokes for the history stack to grow.
  5. Observe whether the overlay remains visually anchored in place as the history expands.

Expected behavior

When using Custom anchor, history growth should preserve the chosen vertical position consistently, just like the stable preset cases.

Actual behavior

The overlay shifts vertically as history grows when using Custom anchor. The reporter noted that only top center and bottom center appear to preserve vertical position reliably, and that this vertical behavior is not carried over to Custom anchor.

Screenshots or screen recording

Original reporter attached screenshots and a screen recording in:
#57 (comment)

Logs or crash report

None.

Additional context

This issue is split from #57 so the original feature request and the follow-up behavioral bug can be tracked independently.

Activity

  1. InSasquatchCountry commented on Aug 4, 2026

    @InSasquatchCountry
    Contributor

    All current anchor point options labeled as stable (✅) and not (❌) with respect to vertical history

    ❌ Top Left
    ✅ Top Center
    ❌ Top Right
    ❌ Center Left
    ❌ Center Right
    ❌ Bottom Left
    ✅ Bottom Center
    ❌ Bottom Right
    ❌ Custom

    Image
  2. self-assigned this
    on Aug 10, 2026
  3. esphynox commented on Aug 10, 2026

    @esphynox
    CollaboratorAuthor

    Hey there, @InSasquatchCountry ! I wanted to clarify what's exact issue of vertical stacking. You marked top center and bottom center anchors as correctly rendered but top left right and bottom left right anchors as incorrect. From what I observe top and bottom anchors regardless of horizontal alignment behave in same way. I see that bottom anchored have more delightful disappearing animation but it still consistent between all horizontal spaces. Am I missing something?

    Top anchors:

    keyty-top-anchors.mp4

    Bottom anchors:

    keyty-bottom-anchors.mp4

  4. InSasquatchCountry commented on Aug 10, 2026

    @InSasquatchCountry
    Contributor

    @esphynox How do I enable numbered mouse event history? Is this a current feature?

    ❌ Top Left
    ✅ Top Center
    ❌ Top Right
    ❌ Center Left
    ❌ Center Right
    ❌ Bottom Left
    ✅ Bottom Center
    ❌ Bottom Right
    ❌ Custom

    In looking back just now, at first I thought I had been referring to an inherited "floor vs ceiling" quality of history rendering, which would no longer apply to the newest release. However I now think I was experiencing a "1 key" vertical shift with history on all but Top/Bottom Center. Whatever it was, it no longer applies and can be disregarded.

    In the 2 minute video below I walk through all anchor options and give my thoughts. There seems to be a vertical shift of a few pixels for history at the top. I think Center Left/Right should be renamed Middle Center/Right. I would need custom anchors to have greater control over history direction "Floor/Middle-Out/Ceiling" to replace my current tool. I personally have no use/interest in horizontal history but noticed that it seems to shoulder up nicely based on content alignment alone. As stated, vertical history would need more control for my purposes.

    note: I found that there is an order of operations constraint for custom positions and alignment worth mentioning in Part 2.
    (You'll need to enable audio to hear my voice 😬)

    2026-08-11 edit: I re-uploaded these just now. They weren't playable in the mobile app.

    anchor_overview_part_01.webm
    anchor_overview_part_02.webm
  5. InSasquatchCountry commented on Aug 10, 2026

    @InSasquatchCountry
    Contributor

    After restoring to default settings (#92) it's clear that the "Top Anchor Vertical Shift w/History" bug shown in anchor.overview_part_1.webm is downstream from key size/type. Some combination of key size and potentially cap-type made the shift unusually pronounced.

    My gut tells me that rounding is either the cause or the solution due to how both the direction of the shift and number of key presses required to trigger the unwanted shift, changes with key cap size.

    Interestingly, the bottom anchor points seem totally unaffected and solid in their anchor.

  6. esphynox commented on Aug 13, 2026

    @esphynox
    CollaboratorAuthor

    I think Center Left/Right should be renamed Middle Center/Right.

    Addressed this one in PR #97. Never thought about actual differences of those words even in native language, lol.

  7. esphynox commented on Aug 14, 2026

    @esphynox
    CollaboratorAuthor

    Created issue for incorrect position of preview window when selecting content alignment - #103 and fixed in PR #102

  8. esphynox commented on Aug 14, 2026

    @esphynox
    CollaboratorAuthor

    Created and fixed feature to control vertical alignment for custom placement - #107

  9. InSasquatchCountry commented on Aug 14, 2026

    @InSasquatchCountry
    Contributor

    MFW someone asks me if I contribute to any open source projects.

    wKjfGYA8bCc1.wKjfGYA8bCc1.webm

    "You know, well, I've submitted a few *ashes cigar* bug reports and feature requests."

    "So no PRs?"

    "YOU CAN'T RUSH THESE THINGS JERRY!"

    Image Image

    ^me having my ideal key caster made for me while coveting contributor credit for what is essentially Hi-Res complaining 🤣

  10. esphynox commented on Aug 15, 2026

    @esphynox
    CollaboratorAuthor

    @InSasquatchCountry, your feedback has been really valuable, so I want to credit you properly. I can add you to the in-app Contributors section myself, or, if you’d like, you can open a PR adding yourself to that list and get the GitHub contributor credit too!

  11. InSasquatchCountry commented on Aug 15, 2026

    @InSasquatchCountry
    Contributor

    🤞 hopefully I did that right 😆

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

bugSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions