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 182638 - FXDComposer does not show some content
Summary: FXDComposer does not show some content
Status: RESOLVED FIXED
Alias: None
Product: javafx
Classification: Unclassified
Component: Unsupported (show other bugs)
Version: 6.x
Hardware: PC Windows XP
: P2 normal (vote)
Assignee: Andrew Korostelev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-24 09:37 UTC by pbenes
Modified: 2010-03-30 13:16 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description pbenes 2010-03-24 09:37:33 UTC
The following is the text of email from nancy.hildebrandt@oracle.com. I believe it will be ok, when new promoted build of JavaFX SDK shall be used, but I filed it anyway just for sure.

This morning I installed the latest stable build of NB, which was 194. I'm still seeing the crosses and no graphic in the artboards test file that I exported to FXZ. Also the ShellCity.fxz file, converted from the AI ShellCity.ai sample, is not showing a preview. I'm not sure if that one has artboards or not--it looks like it does in the original AI graphic, but I only got one content file on export, even though I selected Use Artboards.

The artboards.ai asked me for some legacy choices when I opened it in AI, so I renamed the resulting graphic artboardslegacy.ai.

I've uploaded a bunch of supporting files and screenshots to this location:
http://ipg-jets.sfbay.sun.com/JavaFX/NH/NBPreviewProblem/
That directory contains:
1. NB screenshot of artboardslegacy.fxz
2. The AI dialog box that asks me for legacy decision when I open artboards.ai
3. artboardslegacy.fxz
4. artboarslegacy.ai
5. artboards.ai (from svn)
6. NB screenshot of Shell City.fxz
7. Shell City.fxz
The Shell City.ai file is here:
http://ipg-jets.sfbay.sun.com/JavaFX/NH/forLukas/
Comment 1 Andrew Korostelev 2010-03-30 07:16:35 UTC
fixed.
http://hg.netbeans.org/javafx/rev/165c06c809e4
Comment 2 Andrew Korostelev 2010-03-30 13:16:48 UTC
There also was a problem with Shell City.fxz
Which has 0x0 value in content.fxd
this causes org.xml.sax.SAXParseException: An invalid XML character (Unicode: 0x0) was found in the element content of the document.

Which means ProductionSuite has generated incorrect content.

It is not NB plugin or fxd loader error.
FX viewer also failed to process it with JRE fatal error.