The main run button, it should remain as the debug button for the entire project. So when ever we click on the main run button, the full project should run on debug mode
Let’s leave the other options under the drop down as it is… So we should have all the features as:
Main button - Full project debug
Start project without debug - Right below it as this is required before a release
Start file in debug - We need this feature very much to test individual components
Start File without debug - let’s have it at the very bottom of all four
well others might have different thoughts depending on their view point… This is mine
For the first time (I guess), I will completely disagree with @Lahiru.Fernando
I prefer that the default behavior of the Start button is to Debug File, just like what we have in the previous versions (Run button only runs the current file).
Why? Because we are building components before running the whole project.
A project contains multiple components.
So… we will click the dropdown and choose Start File to run the component.
I believe that there are more times that we run a file than running the whole project.
Hi
Two days back even my team and myself were discussing about this. Glad that we have poll on this now. We would get more ideas on different workbase people.
Great
So I would personally choose with File to be executed when we he start Button is pressed
the reason is
—we have got more than 10 major releases from 2016.1 including FTS and LTS
—all had START to run the current file so it would take some time for those people to get into this update which may (not in big scale) impact when they are designing their workflow
—Though it’s always important to upgrade the application for better performance and configuration we need to consider the people who were set with a practice and even process of executing a file. May be it may sound silly but that’s the practicality.
—Fine so even if the start button is meant for current file execution alone in foreground UI element, we can have like what @J0ska mentioned as that looks cool and won’t impact much, can be used as add on features or we can have like a drop down option as we have now, but start by default for current file execution alone.
I’d say that the Start button should do what it did the last time - i.e. it shiould have memory. So if I click the little arrow and choose to “debug current file”, the next time I click Start it will debug the current file.
And the 1st time I click it it should be some sort of debug. I’d vote for debug project, as new users are not as sophisticated to create multi-file projects, and they will get used to it debugging the whole project.
@loginerror
Ah, makes sense. I would say leave it the way it has always been as the default - so as to not be a completely jarring experience for anyone who is not reading update notes as closely as we are. Then have the drop-downs for the alternative methods and the option to change the default behavior in the settings. Might be more challenging to code the drop-down options to change based on the chosen default behavior, but I’m sure it’s doable