EditorViewHierarchyLogging

Revision as of 14:29, 18 September 2012 by Mmetelka (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)

Logging Options

Note: possibly see FaqSwitchOnLogging,FaqStartupParameters and FaqNetbeansConf how to turn on an extra logging.

There are loggers shared across all the classes of the view hierarchy. They use the following notation:

-J-Dorg.netbeans.editor.view.logtype.level=FINE|FINER|FINEST

where logtype may be one of the following:

  • op - operations performed on the view hierarchy such as model-to-view or view-to-model translations etc.
  • change - tracks changes that trigger structural updates of view hierarchy such as highlighting layer(s) changes.
  • repaint - tracks repaint requested by clients or by the hierarchy itself.
  • paint - debugs how view hierarchy handles paints: size of the clipping area and number of lines that will be painted.
  • span - logs changes of view spans along horizontal and vertical axes and how do they propagate upwards in the view hierarchy.
  • build - tracks view rebuilds in response to changes reported by view factories (namely highlighting layers and code folds).
  • event - logs events fired by view hierarchy
  • settings - logs settings affecting or used by view hierarchy e.g. antialiasing settings.

Consistency Checking

-J-Dorg.netbeans.editor.view.check.level=FINE

checks consistency of the view hierarchy during structural changes. FINER or FINEST levels may be given which increases checks complexity but may decrease performance significantly especially for large documents.

Font and Metrics Information

-J-Dorg.netbeans.modules.editor.lib2.view.FontInfo.level=FINE

logs font(s) being used by the view hierarchy and corresponding metrics info.

Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo