search

JDNdeveloper / Off-By-One

CMPS 115 Project: Jayden Navarro, John Gemignani, Alex Gonzalez, Kevin Cheng, Josh Innis
0 stars 0 forks source link

Make sure when navigating back from an Event that you return to proper fragment #51

Closed JDNdeveloper closed 9 years ago

JDNdeveloper commented 9 years ago

Make sure correct item is selected in nav bar and action bar color is correct as well.

JDNdeveloper commented 9 years ago

Make sure these happen:

  1. change status bar and action bar color.
  2. Make sure nav bar selection is correctly highlighted.
  3. Make sure plus button will direct to correct place.
  4. Make sure action bar text is correct.
  5. Make sure correct array adapter is loaded.
agonza26 commented 9 years ago

@KevinCCheng, make sure to talk to @JoetheSoda about how he set up the constant that stores which page you are on as well as anything else you need to know about this task

KevinCCheng commented 9 years ago

So, Android has a built in stack that keeps track on where it is. The hardware back button does this right but out regular back button doesn't follow it.

We should either make the status bar back button simulate the hardware back button or just remove it if it is not working.

JDNdeveloper commented 9 years ago

Hey Kevin. Actually the back arrow doesn't currently do what we want it to do. We want it to return to the proper fragment in main which it currently doesn't do. Instead it always returns to all lifestyles. On Mar 1, 2015 1:44 AM, "KevinCCheng" notifications@github.com wrote:

So, Android has a built in stack that keeps track on where it is. The hardware back button does this right but out regular back button doesn't follow it.

We should either make the status bar back button simulate the hardware back button or just remove it if it is not working.

— Reply to this email directly or view it on GitHub https://github.com/JDNdeveloper/Off-By-One/issues/51#issuecomment-76589897 .

JDNdeveloper commented 9 years ago

Oh wow. Didn't even try the hardware back button. You're right.

Anyways, the thing that we should be doing is forcing the app to load the proper fragment each time main is called by using the fragmentLocation variable. On Mar 1, 2015 1:44 AM, "KevinCCheng" notifications@github.com wrote:

So, Android has a built in stack that keeps track on where it is. The hardware back button does this right but out regular back button doesn't follow it.

We should either make the status bar back button simulate the hardware back button or just remove it if it is not working.

— Reply to this email directly or view it on GitHub https://github.com/JDNdeveloper/Off-By-One/issues/51#issuecomment-76589897 .

JDNdeveloper commented 9 years ago

Kevin,

I'm pretty sure I know what needs to happen if you want to reassign this task to me.

Up to you. On Mar 1, 2015 1:44 AM, "KevinCCheng" notifications@github.com wrote:

So, Android has a built in stack that keeps track on where it is. The hardware back button does this right but out regular back button doesn't follow it.

We should either make the status bar back button simulate the hardware back button or just remove it if it is not working.

— Reply to this email directly or view it on GitHub https://github.com/JDNdeveloper/Off-By-One/issues/51#issuecomment-76589897 .

JDNdeveloper commented 9 years ago

http://stackoverflow.com/q/12276027/903996

JDNdeveloper commented 9 years ago

Implemented.