Skip to content
This repository has been archived by the owner on Apr 30, 2024. It is now read-only.

Unify appRouter and dialogRouter #74

Closed
wants to merge 2 commits into from
Closed

Unify appRouter and dialogRouter #74

wants to merge 2 commits into from

Conversation

kathyma
Copy link
Contributor

@kathyma kathyma commented May 26, 2016

No description provided.

@kathyma kathyma force-pushed the unify-flows branch 7 times, most recently from eecf3c1 to 638bade Compare May 27, 2016 22:50

@Controller(DialogController.class)
@DaggerModule(DialogModule.class)
@EnterTransition(SlideUpTransition.class)
@ExitTransition(SlideDownTransition.class)
public class Dialog extends Screen {
private byte[] backgroundBitmap;

public void setBackground(BitmapDrawable backgroundDrawable) {
Copy link

@buildbreaker buildbreaker May 27, 2016

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Who should ideally be the one calling this method?

It seems that we are relying on the transition to handle this but I'm not convinced that is the right decision

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The dialog controller is the one calling it right now as it's the one responsible for storing/restoring state. The transition is only responsible for capturing the state before the transition happens and sets the to view accordingly. I considered moving it to UIContainer, but this seems too specific of a view property (BitmapDrawable background) to store/restore on a framework level.

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

Successfully merging this pull request may close these issues.

3 participants