update with ZSA's response to my report of the bugs

This commit is contained in:
2025-09-25 12:40:51 -07:00
parent 0bdedd062a
commit 3dfa967f25
2 changed files with 191 additions and 154 deletions

View File

@@ -172,8 +172,11 @@
is only visible in dark mode.
</li>
<li>
The text doesn't move down for the first time until the bottom line
is fully completed.
<s>
The text doesn't move down for the first time until the bottom
line is fully completed.
</s>
<b>FIXED!</b>
</li>
</ul>
<img
@@ -199,7 +202,7 @@
couldn't find a way to add this key to my Voyager, so I asked ZSA
support. After a little less than 24 hours, they responded with this:
</p>
<blockquote cite="">
<blockquote>
<p>
Hello Ted — thanks for asking! We don't have any keys that
correspond to the Launch2 keycode in Oryx. In the underlying
@@ -224,9 +227,28 @@
corpo speak you'd get from a bigger company.
</p>
<p>
Additionally, I've contacted them about the two Oryx issues, and I was
told it's been passed off to the dev team. I'll update this page if I
get an update or it's fixed.
Additionally, I contacted them about the Oryx issues. Here's their
response:
</p>
<blockquote>
<p>Hi, Ted!</p>
<p>The team has fixed the "invisible text" issue.</p>
<p>
We'll leave the scroll timing as-is for now, but this may be
something to revisit when the team is a little less swamped.
</p>
<p>Thank you!</p>
<p>
<br />
Tisha Stacey,<br />
Customer Service,<br />
ZSA Technology Labs Inc.
</p>
</blockquote>
<p>
Although slightly disappointing, this response is understandable. The
scrolling issue was more of a personal preference, and I can certainly
appreciate that they at least fixed the text issue.
</p>
<h3>The Conclusion</h3>
<p>