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 244941 - Color representing the file version status (Modified, New) are not shown in projects tab during selection
Summary: Color representing the file version status (Modified, New) are not shown in p...
Status: REOPENED
Alias: None
Product: platform
Classification: Unclassified
Component: Nodes (show other bugs)
Version: 8.0
Hardware: PC Linux
: P3 normal (vote)
Assignee: Jan Peska
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-06-08 10:20 UTC by adithyank
Modified: 2014-06-09 07:05 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
screen shot showing projects window with black fore color in tree node of a modified svn file (168.23 KB, image/png)
2014-06-08 10:22 UTC, adithyank 		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 adithyank 2014-06-08 10:20:31 UTC 
Product Version = NetBeans IDE 8.0 (Build 201403101706)
Operating System = Linux version 2.6.32-431.17.1.el6.x86_64 running on i386
Java; VM; Vendor = 1.8.0
Runtime = Java HotSpot(TM) Client VM 25.0-b70

We use SVN repository. After I modify a svn checked-out file, the editor title tab of that file turn to BLUE color and the respective node in the projects window also turns to BLUE color. But, when I select that node in the projects window, then the font color turns to black. i.e., the font color that corresponds to the current versioning label is not shown in the projects window tree node if it is selected. 

The natural expectation is to show color here also...

If you feel that this is a trivial bug, then you can reject it.
Comment 1 adithyank 2014-06-08 10:22:02 UTC 
attached screen shot showing projects window with black fore color in tree node of a modified svn file
Comment 2 adithyank 2014-06-08 10:22:11 UTC 
Created attachment 147608 [details]
screen shot showing projects window with black fore color in tree node of a modified svn file
Comment 3 Ondrej Vrabec 2014-06-08 15:51:15 UTC 
actually the correct behavior, it is impossible to match the correct colors for selected nodes (background and versioning foreground) that do have proper contrast (with all look-and-feels and platforms). In order to at least be able to read the text (e.g. an ignored file on windows would have unreadable name) selected nodes are always painted with the default colors: see bug #233076 for more details

*** This bug has been marked as a duplicate of bug 233076 ***
Comment 4 adithyank 2014-06-08 18:40:34 UTC 
Considering the comments in this bug and Bug #233076, I am giving the following comments

It may first seem like it is not possible to identify the different color combinations for showing the versioning status' colors. It is not uncommon for a developer thinking like this.

But, it is not impossible to write a logic to choose the appropriate background or foreground color based on our color needs in situations like this. I don't feel this logic will be too complicated.

In the process of building a world class IDE for programmers, I am not technically convinced with the given comments against these bugs. This issue needs to be resolved and it cannot be skipped. 

Also, in situation like these, performing steps like below will resolve the issue. We have done some thing like this in one of out products.

1. Now we are changing the forecolor when the file state is changed. But, we can change the background color of the tree node. By default, we can choose some soft colors for these.
2. When background color of a tree node is changed, we can identify a readable forecolor with a simple formula
3. Then, during selection, we can swap the background color and forecolor

This is just a hint. But, some thinking can be applied in this direction to resolve this issue.

-----


This is marked as duplicate of bug #233076. Bug #233076 is marked duplicate against bug #233699.

Bug #233699 is fixed. But, i don't feel that fully solves this problem. This problem still exists and the nature of problem is different. 

I am reopening this issue as I am not fully convinced with the comments. If you still feel that this is duplicate, then pls resolve again...
Comment 5 adithyank 2014-06-08 18:42:52 UTC 
I am sorry for a typographical error. Wherever I used #233699, pls interpret it as #230699
Comment 6 Ondrej Vrabec 2014-06-09 07:05:47 UTC 
> Also, in situation like these, performing steps like below will resolve the issue. We have done some thing like this in one of out products.

> 1. Now we are changing the forecolor when the file state is changed. But, we can change the background color of the tree node. By default, we can choose some soft colors for these.
> 2. When background color of a tree node is changed, we can identify a readable forecolor with a simple formula
> 3. Then, during selection, we can swap the background color and forecolor
Sure, background color could be different for all colors, it is technically possible, however imagine how the UI would look if every node shined with a different background and foreground color. IMO much better and more useful is to enable versioning labels and have the status displayed as text right next to the file name.

Passing to nodes, if they want to play with background and foreground colors and make the IDE into a painting program shining with 80 different shades of gray color, they can.