Textfield doesn't lose focus when other gadgets are interacted with

About Monkey 2 Forums Monkey 2 Development Textfield doesn't lose focus when other gadgets are interacted with

This topic contains 7 replies, has 2 voices, and was last updated by  skn3 2 years, 6 months ago.

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #4514

    skn3
    Participant

    Looking at the code it looks like not all gadgets/views are currently calling  MakeKeyView. So for example if I select a textfield, then select a list item, then the textfield cursor remains.

    #4515

    skn3
    Participant

    P.S. where do you want bug reports, here or on Github issues?

    #4517

    Mark Sibly
    Keymaster

    ListView does not currently respond to key events.

    Mojox is still a WIP, so there will be many ‘holes’ like this in it. Things’ll happen over time, but if you’re after a 100% complete GUI system mojox probably isn’t for you!

    #4520

    skn3
    Participant

    Sorry I have probably given the impression that I am complaining about monkey2. I was just trying to be helpful.

    MojoX is working out great for me at the minute! Really quick to get some basic tool stuff running.

    The bug report in this thread was causing a crash for me. I had a Lambda function that was responding to textfield changes, after clicking the listview and then typing, it was hard crashing the app. I fixed it by manually setting the KeyView in my app code.

    #4526

    Mark Sibly
    Keymaster

    Sorry I have probably given the impression that I am complaining about monkey2.

     

    No problem, just wanted to make extra sure you realized that mojox is currently a bit , erm, idiosyncratic.

    But by the look of the screenshot, you seem to be doing just fine!

    The bug report in this thread

    Link missing?

    #4530

    skn3
    Participant

    Nothing wrong with some idiosyncrasies 😉

    Bug report:

    Well basically just that there doesn’t currently seem to be any Focus/Blur handling for views. Its implemented for items that receive text input, but not for others. So I am able to keep typing in a text field, even after I have clicked a button that should have blurred it.

    As you have suggested this is probably more of a WIP issue then a bug. For now I can just manually add it into bits of my code, but it would be good if all views handled this and then reported OnFocus and OnBlur event callbacks.

    #4531

    Mark Sibly
    Keymaster

    Bug report:

    Ahh, OK, though it was another bug as you didn’t mention a crash originally.

    Any way for me to easily reproduce the crash?

    #4533

    skn3
    Participant

    Ok I have created something that will reproduce. Now that I have isolated it, it turns out that it is actually a bug (and not my own user error) .

    Steps:

    1. press “item2” button
    2. select the text field and position the cursor at the end of the text
    3. press “item1” button
    4. start typing on the keyboard
    5. CRASH
Viewing 8 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic.