Details

    • Type: Task Task
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      i came across this again in the android port of lwuit.
      my default VKB didnt not appear on the screen instead the default android keyboard was used.
      i found out that thorsten used Display.getInstance().setDefaultVirtualKeyboard() while i used setDefaultVirtualKeyboardClass on the VirtualKeyboard class which according to the doc is what i was supposed to do (it was also referred to it by the previously deprecated class/method which i forgot its name now)
      i change the code locally for my app to use both but i dont think its a good thing this ambiguously there need to be 1 point of interaction here.

        Activity

        Hide
        vprise added a comment -

        Did you set this after initializing the display?

        Show
        vprise added a comment - Did you set this after initializing the display?
        Hide
        tempusername added a comment -

        of course

        Show
        tempusername added a comment - of course
        Hide
        chenf added a comment -

        fixed - improve the documentation of this

        Show
        chenf added a comment - fixed - improve the documentation of this

          People

          • Assignee:
            chenf
            Reporter:
            tempusername
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: