text box focuses at start when editing? :/


  1. dan55

    dan55 Well-Known Member

    hi guys,

    this seems to be a common thing now on all current gb roms, but im sure it didnt used to work this way :/

    when editing any text box that already has some text in it, the cursor goes to the front of the field rather than after the existing text as i would expect.

    am i confused in thinking that it used to work differently? :/
    or is there a way to change this behaviour?

    cheers
    dan

    Advertisement
  2. SUroot

    SUroot Well-Known Member Developer

    I cant remember if it worked differently as ive been on gb for a long time, but I confirm the issue and that it is VERY annoying.
  3. dan55

    dan55 Well-Known Member

    phew! thought I was losing it there :-D
    ....any chance of a hack? ;-)
  4. SUroot

    SUroot Well-Known Member Developer

    Maybe but I myself have no idea what bit of code controls that
  5. dan55

    dan55 Well-Known Member

    oh ok no worries :)

    im guessing the google coders forgot to add the bit where it checks for textbox contents when setting focus :D

    cheers
  6. SUroot

    SUroot Well-Known Member Developer

    Maybe. I just dont know where to look. dGB is 45,616,039 lines of code :)
  7. dan55

    dan55 Well-Known Member

    F' me! thats a lotta lines :eek: :D

    btw: on a general rom type note: any ideas what might cause apps to fail/close, but not show FC error? can be any app at any point

    sorry a bit vague i know :/ :)

    ....oh, dont worry, its not dGB :)

    cheers
  8. SUroot

    SUroot Well-Known Member Developer

    ummm. Not really. Tried running "dmesg" from terminal after a suspected FC?
  9. dan55

    dan55 Well-Known Member

    ok thanks - does that do similar to alogcat?
  10. SUroot

    SUroot Well-Known Member Developer

  11. dan55

    dan55 Well-Known Member

    ah ok cool - thanks
    btw: is any terminal app better than another to do this ? ta
  12. SUroot

    SUroot Well-Known Member Developer

  13. dan55

    dan55 Well-Known Member

    kool ta
  14. dan55

    dan55 Well-Known Member

    theres a lot of Sony mentioned in it :/ :D
  15. SUroot

    SUroot Well-Known Member Developer

  16. dan55

    dan55 Well-Known Member

    :/
    sony_tft lines - sony make the screen? :/
  17. SUroot

    SUroot Well-Known Member Developer

    only the slcd ones. Its nothing to worry about anyway.
  18. dan55

    dan55 Well-Known Member

    ah right - sorry - type of screen - i get you - a bit slow there! :D
  19. dan55

    dan55 Well-Known Member

    hi Dan.
    had a few odd closes just now. ran dmesg but not too
    sure what I'm looking for. I did see this at the end of log
    though. cheers

    g), 29.3 C, 1225 mAh
    <6>[ 1546.674957] binder: 181:187 transaction failed 29189, size 56-0
    <6>[ 154
  20. SUroot

    SUroot Well-Known Member Developer

    I dont think dmesg is going to give us any clues in this case. It was a longshot. May have to run a logcat constantly :(
  21. dan55

    dan55 Well-Known Member

    :) ok no worries. ta

    I thought I could just run alog after the event to get logs?
  22. SUroot

    SUroot Well-Known Member Developer

    Theres no reverse logcat, no. dmesg goes backwards but it doesnt capture everything a logcat does,
  23. dan55

    dan55 Well-Known Member

    ah ok thanks.

    so when devs say open alog and get logs after event. that isn't going to work :-\
  24. SUroot

    SUroot Well-Known Member Developer

    not with a logcat, no. Logcat records from the instant of creation until you stop it.
    dan55 likes this.
  25. dan55

    dan55 Well-Known Member

    ah ok thanks.
    maybe comms issue between me and dev :-D
    cheers

Share This Page