Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tracking bugs in the fragment_wip branch #47

Closed
ubergeek42 opened this issue Jul 26, 2012 · 3 comments
Closed

Tracking bugs in the fragment_wip branch #47

ubergeek42 opened this issue Jul 26, 2012 · 3 comments

Comments

@ubergeek42
Copy link
Owner

This exists only to track known issues with the fragment_wip branch. Add a comment for any new issues/or comment if they've been fixed.

Current List:

  • If you receive a notification, even after clicking on it, clicking the ongoing notification takes you back to the same buffer(e.g. if you get highlighted in #weechat, click the notification and then leave, but come back to weechat through the notification bar, you will be taken back to #weechat, instead of the buffer list). - fixed as of 7/26/2012
  • The Hotlist dialog has a grey background on my phone, and the text color is white, which makes it impossible to read.
  • Counts for unread/highlights sometimes show negative.
  • the back button doesn't get you to the buffer list from inside a buffer. This is a regression.
    • re-implemented for now, but not sure this will be the final behavior.
  • when I quit without disconnecting, I get a crash notice. Disconnecting before quitting works fine.
    • was a bug with 3.0+. Fixed in latest
  • sometimes the ActionBar shows the last active channel instead of Weechat when returning to the buffer list.
@torhve
Copy link
Contributor

torhve commented Jul 26, 2012

The Hotlist dialoge has a grey background on my phone, and the text color is white, which makes it impossible to read.

@norrs
Copy link
Contributor

norrs commented Aug 4, 2012

Built yesterday from master, tried to just "resume" use of app after it's been in my pocket for a while when I was outside today

08-04 15:18:34.975: ERROR/AndroidRuntime(3709): FATAL EXCEPTION: main
java.lang.NullPointerException
at com.ubergeek42.WeechatAndroid.fragments.BufferFragment.initView(BufferFragment.java:169)
at com.ubergeek42.WeechatAndroid.fragments.BufferFragment.access$300(BufferFragment.java:39)
at com.ubergeek42.WeechatAndroid.fragments.BufferFragment$1.onServiceConnected(BufferFragment.java:139)
at android.app.LoadedApk$ServiceDispatcher.doConnected(LoadedApk.java:1068)
at android.app.LoadedApk$ServiceDispatcher$RunConnection.run(LoadedApk.java:1085)
at android.os.Handler.handleCallback(Handler.java:605)
at android.os.Handler.dispatchMessage(Handler.java:92)
at android.os.Looper.loop(Looper.java:137)
at android.app.ActivityThread.main(ActivityThread.java:4575)
at java.lang.reflect.Method.invokeNative(Native Method)
at java.lang.reflect.Method.invoke(Method.java:511)
at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:789)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:556)
at dalvik.system.NativeStart.main(Native Method)

@ubergeek42
Copy link
Owner Author

Closing as more or less complete. Most of these have been resolved. Any additional bugs should be filed independently.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants