This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 262195 - Why does IDE propose to create a project when I try to run a binary from an open project?
Summary: Why does IDE propose to create a project when I try to run a binary from an o...
Status: REOPENED
Alias: None
Product: cnd
Classification: Unclassified
Component: Project (show other bugs)
Version: 8.2
Hardware: All All
: P3 normal (vote)
Assignee: Vladimir Kvashin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-23 21:02 UTC by Vladimir Kvashin
Modified: 2016-07-22 18:28 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
dialog (23.98 KB, image/png)
2016-05-23 21:02 UTC, Vladimir Kvashin 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Vladimir Kvashin 2016-05-23 21:02:17 UTC 
Create a sample project (Pi, for example). Build it. In Files tab, find it's binary and double click it, or select "Run" or "Debug" from context menu. A large dialog appears (see attachment); and the "Project" field by default is... guess, what's there? "Create new project".

Well, my original scenario was - the project from existing code, with "build result" field not set, but the binary resides inside. Even in this case IDE shouldn't behave that way. 

It should propose a project binary resides in.
Comment 1 Vladimir Kvashin 2016-05-23 21:02:55 UTC 
Created attachment 159849 [details]
dialog
Comment 2 Vladimir Kvashin 2016-05-23 21:11:45 UTC 
I should probably reopen issue 227793 instead of filing this one.
Comment 3 Alexander Simon 2016-06-15 10:45:10 UTC 
Short answer: by design.
Use launchers for run binary in project context.
Comment 4 Vladimir Kvashin 2016-07-21 21:08:03 UTC 
Alexander, from *user* perspective, I can not understand this "by design".
(From my personal perspective I can - but this does not matter at all).
Or, well, I can, but this tempts me to say a few words about that design... and I'm not sure these words will be politically correct.

I mean that I put on my users hat. Not my developers hat.

Even if I try hard I (from *user* perspective) can not understand this.

As a user, I can not understand that 
- I created a sample project
- I built it
- I invoked "run" on build result
- IDE proposes me to create a project

WTF project should I create? - will user ask - I've just created one! And you (IDE) can not blame me that I created a strange project - that's your own sample!

If you mean this is not that important - please set milestone to "next". Or, at worst, if you think this is not important at all, let's set it to P4.

Although I think this is at least P3. With managed projects this way of doing things is weird. With unmanaged - especially if several binaries are created during make - it's not.