Burhanuddin Rashid

Hmm...Good point. Need to check.

I think having an API where the target platform is checked by the `BuildContext` will help to replace the variant in testing using `variant:` param in `testWidget`. More [here](https://medium.com/geekculture/using-platform-variants-when-testing-flutter-widgets-d3a750d452f0) Something...

@ValentinVignal This is also a fair solution. But I don't think it's backward compatible and might break a lot of code if used extensively in the app. Something like this...

> @ValentinVignal This is also a fair solution. But I don't think it's backward compatible and might break a lot of code if used extensively in the app. Something like...

> @burhanrashid52 Yes my suggestion is a breaking change, but if you increase the version number to `4.0.0` and mention it in the change logs it should be fine right...

Hmm... Maybe using a static instance inside the static `open` method might solve both issues.

Added a comment [here](https://github.com/crazecoder/open_file/issues/180#issuecomment-1044078947)

Ah. I missed that. Thanks. But for that approach, I need to make the widget `Stateful`. I was looking for a way to build this using CalendarBuilder and keeping my...

Seems like the duplicate of #41 Check my [comment](https://github.com/burhanrashid52/PhotoEditor/issues/41#issuecomment-396121962).

Can you please share more details.