-
Notifications
You must be signed in to change notification settings - Fork 1.7k
launch selection rather than last if selection is an application [+4] #2730
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
When the user clicks the "big green run button", I think that we should always "run last" unless the currently selected file is a Dart application (has a main() method) in which case we should run the selected application. See also http://code.google.com/p/dart/issues/detail?id=2499 |
Changed the title to: "launch selection rather than last if selection is an application [+1]". |
It is important that the green button behavior not be surprising. Always running last when you have selected a runnable Dart file is very surprising and unexpected. |
+1 Or after just creating a new project... Which will usually come to the same thing. |
[user feedback] it would be nice if when we click Run, it runs the app where the cursor is positioned or the file that is being displayed in the editor rather than what was Run before Removed Priority-Medium label. |
[hackathon comments] (from jmesserly@ ... taking notes at hackathon) Launch configurations seem to require a lot of setup. It'd be much easier if a there was a "JS in browser" and "Dartium" option by default. Also everyone seems to be trying to right click on the entry point and run it. Finally sometimes "run" doesn't seem to have the right effect (or any effect). It's like it is stuck on an old configuration or something like that. (not sure the details of how to reproduce this one) Changed the title to: "launch selection rather than last if selection is an application [+3]". |
Howdy, editor folks. (KathyW here) I'm starting to beef up the Dart Editor docs, but I don't know what to write about launches. The behavior isn't what I expected. Here's what happened:
I don't know how to get the server app to run, other than painfully creating a new launch for it. Another surprise. CHECKED MODE is still off. For some reason, I thought it was now on by default. I guess only debugging is on by default. What's the story on launching apps (aside from the first app)? Thanks, -k- Changed the title to: "launch selection rather than last if selection is an application [+4]". |
As per all the feedback, changing Run button behavior to
|
Issue #2499 has been merged into this issue. |
https://chromiumcodereview.appspot.com/10270017/ Added Fixed label. |
New commits: git log --format="%C(auto) %h %s" 900e796a37fd9f68de9dd183cf4798fe5f055eaa..4ca4767a6c00b2dadecdaee9a4866dae40ef25f2 4ca4767a Added a dart pub outdated --transitive option (#2731) 6b145bd6 Deprecate --server argument to `pub publish` and `pub uploader`. (#2697) 7737023a don't warn if previous prerelease was null safe (#2730) 62f92838 Improve outdated --mode=null-safety (#2724) cc589ec3 Change message for no Latest resolution (#2729) 656803e9 Require sdk constraint (#2718) 8309d877 Added test that dev_dependency does not trigger null-safety warnings when publishing (#2727) 332ea049 Remove warning about mixed mode. (#2723) a98a1f23 Simplify null-safety analysis in `pub outdated --mode=null-safety` (#2721) 5fba2015 Outdated null safety implies prereleases (#2722) fb9ec4af Fixed bug in yaml_edit (#2703) Change-Id: I22a084aee06542e04a272269fb0134f0ac62f779 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/170690 Commit-Queue: Sigurd Meldgaard <[email protected]> Reviewed-by: Michael Thomsen <[email protected]> Reviewed-by: Jonas Jensen <[email protected]>
[user feedback]
Newly created application not been set as main project/application. When I open a new application and try to run it using the green play button or “ctrl+r” the previous application is running, to run the application for the first time i need to right click and select run as---> dartium launch.
The text was updated successfully, but these errors were encountered: