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 258550 - Can't set Project Properties
Summary: Can't set Project Properties
Status: RESOLVED FIXED
Alias: None
Product: cnd
Classification: Unclassified
Component: Editor (show other bugs)
Version: 8.1
Hardware: PC Windows 8.1
: P3 normal (vote)
Assignee: issues@cnd
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-27 23:28 UTC by John_Parke
Modified: 2016-03-28 12:27 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Screen Shot of IDE (842.85 KB, image/png)
2016-03-27 23:28 UTC, John_Parke 		Details
messages.log (279.48 KB, application/octet-stream)
2016-03-28 11:54 UTC, John_Parke 		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 John_Parke 2016-03-27 23:28:30 UTC 
Created attachment 159018 [details]
Screen Shot of IDE

I have a C++ project where I cannot set the project properties.

The project is a remote development project (Linux based from Windows 8.1).
The project is under Git control.

When I right click on the project Icon, nothing happens; no pop-up or drop-down box of any kind. The project icon appears to have a ? mark in it.

When I first created the project, I could right click the project icon and set properties, or do a "code assistance - reparse project". This no longer works.

To attempt to fix, I deleted all the cache folders on Windows, deleted the nbproject folder from the project, and deleted the dlight_root folder on Linux.

Nothing seems to work.

Any help would be greatly appreciated.

Thanks,

John
Comment 1 Alexander Simon 2016-03-28 07:14:30 UTC 
Please, attach IDE message log (http://wiki.netbeans.org/FaqLogMessagesFile)
and threads dump (http://wiki.netbeans.org/GenerateThreadDump)
Comment 2 John_Parke 2016-03-28 11:54:40 UTC 
Created attachment 159021 [details]
messages.log
Comment 3 John_Parke 2016-03-28 12:27:29 UTC 
I went into "tools" "options" and went through most of the tabs looking for any setting that might possibly affect this problem. When I exited the option, the problem was fixed, even though I did not change any settings.