Replies: 6 comments 6 replies
-
|
I was mistaken about the size of the font on the smaller keyboard. It does not need to be that large, and it would be better if it was smaller because I can only see part of some of the buttons. Also, re: the smaller keyboard. I think that it would be ideal, if as Sophie suggested, it could be a pop up. And if it could float so that I could move it around and also pin it that would be great. But, if not, it would be better to have it positioned in the middle at the top, just under a message window. |
Beta Was this translation helpful? Give feedback.
-
|
Hey Patrick - does this look more like what you are thinking for the smaller keyboard? I am not sure that we can emulate "moving it around" though @gbishop I suppose I could make tab controls with it in different places but not sure how Patrick would then "move" it. |
Beta Was this translation helpful? Give feedback.
-
|
I bet we could do something with the ability to use state variables as
properties. I hallucinate that we could offer the ability to move the
keyboard around in small steps with button pushes (or whatever).
…On Thu, Jan 2, 2025 at 8:22 PM Sofia B-G ***@***.***> wrote:
Hey Patrick - does this look more like what you are thinking for the
smaller keyboard? I am not sure that we can emulate "moving it around"
though @gbishop <https://github.com/gbishop> I suppose I could make tab
controls with it in different places but not sure how Patrick would then
"move" it.
Grid3_Patrick_1_2_25.zip
<https://unc-project-open-aac.github.io/OS-DPI/?fetch=https://github.com/user-attachments/files/18295750/Grid3_Patrick_1_2_25.zip>
—
Reply to this email directly, view it on GitHub
<#260 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABQK7F4QE2RP7TZXC32PQL2IXQ4TAVCNFSM6AAAAABT7TAUCOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCNZSGE4DINI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***
.com>
|
Beta Was this translation helpful? Give feedback.
-
|
Here is a quick hack using the < and > keys in the lower row on the tiny keyboard. I'm using the Excel-like feature that allows values of properties like "Scale" to be expressions by preceding the expression with an equal sign. |
Beta Was this translation helpful? Give feedback.
-
|
oh very cool! |
Beta Was this translation helpful? Give feedback.
-
|
Hey @gbishop @KeyPatrick pointed out that dwell is still active on the small keyboard when the intention is to use the mouse to click. I tried using conditions to set the point and dwell to only work when $HeadMouse = "on" - that seems to have set it so that the dwell time remains on the large keyboard, but on the small now it dwells almost automatically. Any ideas? |
Beta Was this translation helpful? Give feedback.
-
|
Try this. I added the condition to every handler. |
Beta Was this translation helpful? Give feedback.
-
|
Sorry for the delay. Our oven died in a very dangerous way and I've been removing it in preparation for a new one. |
Beta Was this translation helpful? Give feedback.
-
|
Oh gosh that is scary! And thanks for the solution :) |
Beta Was this translation helpful? Give feedback.
-
|
Hopefully you were all safe Gary. I will try out the change. I haven't noticed any delay from you all. This has been a very speedy way to work together and you are all making changes so fast, it is amazing. |
Beta Was this translation helpful? Give feedback.
-
|
@gbishop already stuck with the modal - I created it but when I linked it to the gear button in actions it opens to a white page not the grid. Also, how can I change the relative position of the modal so that you can still see the keyboard? Seems like I need to see where the keyboard is moving in real time for it to be effective. |
Beta Was this translation helpful? Give feedback.
-
|
You are setting $tabControl to "move" but there is no tab panel with that
name...
Instead you should be opening the Modal by setting $modalOpen to 1.
…On Fri, Jan 10, 2025 at 3:00 PM Sofia B-G ***@***.***> wrote:
@gbishop <https://github.com/gbishop> already stuck with the modal - I
created it but when I linked it to the gear button in actions it opens to a
white page not the grid. Also, how can I change the relative position of
the modal so that you can still see the keyboard? Seems like I need to see
where the keyboard is moving in real time for it to be effective.
Grid3_Patrick_1_10_25_v2.zip
<https://github.com/user-attachments/files/18381836/Grid3_Patrick_1_10_25_v2.zip>
—
Reply to this email directly, view it on GitHub
<#260 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABQK7A44XAAXNYR2VSEKJL2KARG5AVCNFSM6AAAAABT7TAUCOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTCOBQGIYDKNY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***
.com>
|
Beta Was this translation helpful? Give feedback.
-
The following represents a simulation user interface (UI) for a project aimed at designing a scalable keyboard that can be efficiently adjusted based on positioning and desired access method - specifically a large, eye gaze access-enabled keyboard filling the bottom two-thirds of the screen when in a seated position and a scaled down, trackball access-enabled comparable keyboard when lying down. The link below provides a simulation of a UI similar to the co-designer's current system (Text Talker from Smartbox) to explore the needed functionality. The scaled-up version in the current iteration enables head-tracking using the computer's built-in camera as an initial simulation.
To explore the functionality, load the simulated UI using the link below:
https://unc-project-open-aac.github.io/OS-DPI/?fetch=https://github.com/user-attachments/files/18086076/Grid3_Patrick_12.10.24.zip
Use the following keys on an external keyboard to explore the simulated functionality:
Beta Was this translation helpful? Give feedback.
All reactions