dkter / aaaaa Goto Github PK

Had to switch my keyboard from yours back to AnySoft even just to type this issue.

Does this app have any real purpose or just created for fun sake?

In the keyboard test field, A and are still accepted in minimalist mode, even though it shouldn't be possible to type them. This might mean that a malicious user changed the entry method.

aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

These days there's no excuse for not supporting the full diversity of users and the ways they need to say "a". Support for non-Latin scripts could start with А (Cyrillic) and Α (Greek), but also あ, ア, 啊, ㅏ, अ, ა, ᐊ, and perhaps someday even ᚨ and ᚐ.

there are some weird symbols at the bottom of the keyboard, probably due to incompatible encoding, making it impossible to read what is supposed to be written there. that can be seen on the screenshot below. a fix to something like aaaaa would be welcome.

I would like for the keyboard to repeatedly enter 'a's when I long press the 'a' key.

I've already created a prototype:

It's still a little rough around the edges, but I was wondering if you would accept a pull request once I clean up the code.

aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa_aaaaaaaaaaaaaa_

Please fix this it's literally unusable if I tap something but type something else how am I supposed to tell what letter I'm typing

build by glarses in his latest video. yes, it actually types a for every a key. thought you might like this =)

It is a Amazing App 👍 but sadly it does not have a dark theme. It will great if app have dark theme or follow-system to change between light and dark theme.

aaaaa

AAA aaaaaa aaaa

we need bbbbb and ccccc and others, having just aaaaa promotes racism towards other letters

• When executing this sequence of actions, there is a loss of data in the activity HomeActivity:

1. KeyEvent(name=BACK)
2. IntentEvent(intent='am start io.github.dkter.aaaaa/io.github.dkter.aaaaa.MainActivity')
3. ScrollEvent(direction=FULL_RIGHT)
4. IntentEvent(intent='am start io.github.dkter.aaaaa/io.github.dkter.aaaaa.MainActivity')
5. Cap01: capture screen properties before rotation
6. DoubleRotationEvent
7. Cap02: capture screen properties after rotation
8. Cap01 != Cap02 (changed some properties)

• MainActivity: closed the app.

Before and after double screen rotation

• MainActivity: pop-up menu disappears

Before and after double screen rotation

A data loss problem occurs when data is accidentally deleted or state variables are accidentally assigned with default or initial values. This issue is related to the activity's lifecycle (1). When a screen rotation occurs, the activity is destroyed and resumed. Data loss will happen if the developer does not save the variables before the destruction and restore them after creation. To avoid this, the developers have to implement both the logic necessary to save the activity state in the onSaveInstanceState() callback method and the logic to resume its state in the onRestoreInstanceState() callback method.
Another way to avoid data loss problems is to use the view model, designed to store and manage UI-related data in a lifecycle-conscious way (2).

Note:

• Double screen rotation: It is executed twice to reach a state that should be exactly the same as the screen before if no data loss occurred.
• A data loss problem occurs when data is accidentally deleted or state variables are accidentally assigned with default or initial values.

1. https://developer.android.com/guide/components/activities/activity-lifecycle
2. https://developer.android.com/topic/libraries/architecture/viewmodel

aaAAAAAAaaaaaaaAAAAAAAaAAAaaA

There's an app I use that really likes to focus the text box and open the keyboard when I'm trying to browse other sections of it. My regular keyboard, as you say, has way too many keys, so it ends up filling almost all the screen, so I have to dismiss it each time it appears in order to use the app. With aaaaa, there is only one key and it only takes up a small part of the screen, allowing me to just leave it open and use the app in the top half of the screen.

So it turns out the value in aaaaa is looking at it and not touching it. Which is... probably what I'd expect from the beginning. Marvelous.

Simplicity wins yet again. Thank you, and have an AAAAA day!

What I expected: aaaaaaaaaaaaaaaaaaaaaaaaaa!

What actually happened: aaaaaaaaaaaaaaaaaaaaaaaaaa

This is wonderful software, but it's very disappointing that it doesn't have an exclamation point. There are some cases where I would like to express excitement, but it does not seem to be available. Do you think we could get an exclamation point? I understand this software is made with free time, so please take as much time as you need.

Keyboard as it is is not usable. I need accented characters, such as à or â. Please urgently fix.

This may be an absolutely silly idea. But I was thinking if a average user was to hold down A they could choose from a selection of A's such as:
𝒶
ɐ
ã
and I don't mean to get political or anything, but possibly
@

aaaaaaaaaaaaaaaaaaaaaaaaaa

aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

There should be a smart suggestions panel that suggests previously typed sequences of a to speed up the typing experience even more!

Please add a super compact mode that removes the backspace and enter keys. All we really need is aaaaaaaaaaaaaa

While a alone gives ample room for communication, even simply adding w widely expands the range of possibilities. Consider: awawawa, awwwww, waaaaa, etc.

This would be create a positive future for the app, expanding it's uses and accessibility, for example it would make it more accessible to dolls. Thank you for understanding.

This great app deserves a good icon, so I gave it a try:

Or you could add a second option for the letter "k" and make the ultimate passive-agressive keyboard.

For greater accessibility, voice typing should enable more people to express themselves digitally, as well as to everyone nearby, by typing a based on the duration of the voice input.

Many keyboards have a feature where you can swipe across the keyboard, and it will input text accordingly. See attached picture for reference.

Do you think this is too much bloat or is it a feature worth implementing?

Keyboards that use this feature: FlorisBoard, ASK, GBoard, Swift Keyboard,...