- 19 Apr, 2017 7 commits
-
-
Chinmay Garde authored
* Remove FadeTransition from _MountainViewFadeTransition. * Update tests.
-
xster authored
-
Hans Muller authored
-
Ian Hickson authored
-
Devon Carew authored
-
Adam Barth authored
Turns out we have many immutable classes. Fixes #6892
-
John McCutchan authored
- [x] Switch the reassemble timeout to 5 seconds. - [x] Print a status message if reassemble fails: ``` Performing hot reload... Reassembling app.flx$main took too long. Hot reload may have failed. Reloaded 0 of 418 libraries in 5,322ms. ``` Fixes #9316 Fixes #8861 Fixes #8857 Fixes #8856
-
- 18 Apr, 2017 17 commits
-
-
Brian Slesinsky authored
-
Mikkel Nygaard Ravn authored
-
Ian Hickson authored
-
John McCutchan authored
- [x] Refresh FlutterViews before issuing a hot reload / restart Fixes #7248
-
Hans Muller authored
-
Devon Carew authored
-
Mikkel Nygaard Ravn authored
-
John McCutchan authored
- [x] Resume the isolate before performing a hot restart. Fixes #8923
-
Hans Muller authored
-
Mikkel Nygaard Ravn authored
-
Ian Hickson authored
-
Michael Goderbauer authored
-
xster authored
* Make Cupertino page transition elevation animated too * Rename and change physical model to a decorated box * Tests * Add a comment * still need to handle null in the tween somewhere * nits * Tweens evaluate to the actual begin/end instances. Let them be non-null * Rename no decoration to none
-
Michael Thomsen authored
-
Mikkel Nygaard Ravn authored
-
Sarah Zakarias authored
-
Sarah Zakarias authored
-
- 17 Apr, 2017 10 commits
-
-
Hans Muller authored
-
John McCutchan authored
- [x] Catch SocketErrors and handle them gracefully. - [x] Print 'Lost connection to device' when the service protocol connection is severed unexpectedly. - [x] Print 'Application finished' when the application exits otherwise. After this PR: ``` Launching lib/main.dart on Nexus 7 in debug mode... Running 'gradle assembleDebug'... 1.2s Built build/app/outputs/apk/app-debug.apk (21.7MB). Syncing files to device... Application finished. DevFS sync failed. Lost connection to device: SocketException: OS Error: Connection refused, errno = 111, address = 127.0.0.1, port = 53062 Could not perform initial file synchronization. ``` Fixes #6705
-
Zachary Anderson authored
-
Phil Quitslund authored
Follow-up from #9422
-
Phil Quitslund authored
Fixes: https://github.com/flutter/flutter-intellij/issues/914
-
John McCutchan authored
- [x] Skip scanning the file system if we already have the Dart dependency set. Fixes #9376 ``` Performing hot reload... Reloaded 1 of 418 libraries in 888ms. Performing hot reload... Reloaded 1 of 418 libraries in 871ms. ** UNTAR dragontail under project root ** Performing hot reload... Reloaded 0 of 418 libraries in 443ms. ** UNTAR dragontail under lib/ ** Performing hot reload... Reloaded 0 of 418 libraries in 385ms. ```
-
John McCutchan authored
The first hot reload does a bunch of work that we used to hide behind the loader screen. This PR changes the messsage printed to the user on the first reload from: 'Performing hot reload...' to: 'Initializing hot reload...' Subsequent reloads say 'Performing hot reload...'
-
Hans Muller authored
-
Chris Bracken authored
Also switches to single quotes for consistency with surrounding code.
-
Dwayne Slater authored
-
- 16 Apr, 2017 1 commit
-
-
Brian Slesinsky authored
When invoked from the command line, relative paths aren't typically used, but they are when invoked from within IDEA and prevents IDEA from reading the files. Also, remove flutterPackagesDirectory since it's not used
-
- 15 Apr, 2017 4 commits
-
-
Zachary Anderson authored
-
Brian Slesinsky authored
IDEA gets confused unless the filename matches the project library name, including getting the case right.
-
Ian Hickson authored
With this patch, you can do: ```dart Future<Null> foo() async { try { await controller.forward().orCancel; await controller.reverse().orCancel; await controller.forward().orCancel; } on TickerCanceled { // did not complete } } ``` ...in a State's async method, and so long as you dispose of the controller properly in your dispose, you'll have a nice way of doing animations in sequence without leaking the controller. try/finally works as well, if you need to allocate resources and discard them when canceled. Simultaneously, you can do: ```dart Future<Null> foo() async { await controller.forward().orCancel; await controller.reverse().orCancel; await controller.forward().orCancel; } ``` ...and have the same effect, where the method will just silently hang (and get GC'ed) if the widget is disposed, without leaking anything, if you don't need to catch the controller being killed. And all this, without spurious errors for uncaught exceptions on controllers.
-
Yegor authored
-
- 14 Apr, 2017 1 commit
-
-
Hans Muller authored
-