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 239624 - No syntax highlighting starting new JavaFX project after initial launch
Summary: No syntax highlighting starting new JavaFX project after initial launch
Status: RESOLVED WORKSFORME
Alias: None
Product: editor
Classification: Unclassified
Component: Painting & Printing (show other bugs)
Version: 8.0
Hardware: PC Windows 7
: P3 normal (vote)
Assignee: Miloslav Metelka
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-18 19:27 UTC by swpalmer
Modified: 2014-03-12 17:31 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
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 swpalmer 2013-12-18 19:27:42 UTC 
Product Version = NetBeans IDE Dev (Build 201312170002)
Operating System = Windows 7 version 6.1 running on amd64
Java; VM; Vendor = 1.8.0-ea
Runtime = Java HotSpot(TM) 64-Bit Server VM 25.0-b62

First launch of dev build.  Imported settings from 7.4.  Loaded the last set of projects.  I made a new JavaFX Application project and the source editor window with my Java code showed no syntax highlighting at all.  Just black on white like a plain text editor.
Comment 1 swpalmer 2013-12-18 19:34:01 UTC 
Note that while continuing to play with this editor window I found that code completion is not working for anything, always resulting in "No Suggestions".  It's like the editor doesn't understand that it is editing Java Code.  Yet at the same time it is show yellow hint underlines , red error underlines, and markers in the gutter for interface implementations (I) and errors, etc.
Comment 2 swpalmer 2013-12-18 19:36:55 UTC 
After a restart of the IDE the syntax highlighting is back and auto-complete is working.  Seems to be an issue only for the initial launch.
Comment 3 swpalmer 2014-03-12 17:31:44 UTC 
I have not seen this in recent builds.  Closing as 'works for me'.