Dec 3 | 7:25 PM |
Mark M. | has entered the room |
Mark M. | turned on guest access |
Paul Y. | has entered the room |
Mark M. |
hello, Paul!
|
Mark M. |
how can I help you today?
|
Paul Y. |
Hi Mark! I'm having a bit of a problem trying to implement my own fragment inside view pagers
|
Paul Y. |
I feel like I might be losing context perhaps?
|
Mark M. |
I could use some context about you losing context :-)
|
Paul Y. |
oh I'm sorry I just realized that you actually answered my question on SO
|
Paul Y. | |
Mark M. |
ah, yes
|
Mark M. |
you use the SO bump
|
Mark M. |
er, you used the SO bump
|
Paul Y. |
hehe yes I didn't have a chance to check back at my desk until just now
|
Mark M. |
I don't know for certain that the nested-fragment issue is the source of your problem, but I'd start there
|
Paul Y. |
dah I wonder if it was that simple
|
Paul Y. |
what made it hard to debug was that it would work infrequently
|
Paul Y. |
sometimes it would update the correct viewpager, sometimes it wouldn't
|
Paul Y. |
BTW, you had answered an earlier question a long time ago which had made me wonder who this "commonsware" guy was
|
Dec 3 | 7:30 PM |
Paul Y. |
thank you for being so helpful!
|
Mark M. |
you are very welcome
|
Mark M. |
if that doesn't solve the problem, post a comment on my answer
|
Paul Y. |
okay will do! I'll have to spin it up when I get back to my office tomorrow
|
Paul Y. |
thanks again!
|
Mark M. |
if you have another question, go right ahead -- nobody else is lined up at the moment
|
Paul Y. |
okay thanks! Actually I just read your last sentance on SO
|
Paul Y. |
what would be in place of the detail fragment?
|
Mark M. |
um, just the widgets that right now the fragment manages
|
Paul Y. |
in order to avoid nested fragments
|
Mark M. |
when the user taps on a different work order, you update the widgets that are there with the new contentes
|
Mark M. |
er, contents
|
Mark M. |
rather than wiping them out and replacing them with brand-new widgets in a brand-new fragment
|
Dec 3 | 7:35 PM |
Paul Y. |
wow okay
|
Paul Y. |
just to understand in my "context", I would actually just get rid of the detail fragment and work with the details as a widget inside PageFragment itself?
|
Mark M. |
well, I presume that the details is more than just a single widget
|
Mark M. |
but otherwise, yes
|
Mark M. |
now, I don't know what your vision is for your UI on smaller screens
|
Mark M. |
the screenshot that you posted in the SO question is clearly tablet-sized
|
Paul Y. |
well fortunately I know my target audience, which will be tablets
|
Mark M. |
oh, well, that's easy enough
|
Paul Y. |
I have been toying with the idea of a master/detail flow
|
Paul Y. |
which was why I did that detail fragment
|
Paul Y. |
and then worked from that, to a viewpager sliding tabs
|
Mark M. |
there's nothing wrong with using a ViewPager
|
Mark M. |
there's nothing wrong with master-detail
|
Mark M. |
there's nothing in theory wrong with having master-detail inside of pages of a ViewPager
|
Mark M. |
but wild horses can't get me to use nested fragments
|
Paul Y. |
haha
|
Paul Y. |
no I like that though much better
|
Paul Y. |
especially when it comes to saving states
|
Paul Y. |
and the whole android life cycles
|
Paul Y. |
Thanks again Mark! I'll have to give this a shot tomorrow, I'll be curious if the childfragmentmanager was my hiccup
|
Dec 3 | 7:40 PM |
Paul Y. |
but I might have to just alter my program altogether anyways now
|
Paul Y. |
thanks again! ttyl!
|
Mark M. |
good luck!
|
Dec 3 | 8:00 PM |
Paul Y. | has left the room |
Dec 3 | 8:30 PM |
Mark M. | turned off guest access |