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 62717 - Filter out properties and constants that don't exist in target platform
Summary: Filter out properties and constants that don't exist in target platform
Status: NEW
Alias: None
Product: guibuilder
Classification: Unclassified
Component: Code (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: issues@guibuilder
Depends on:
Reported: 2005-08-20 17:42 UTC by meliandra
Modified: 2007-08-08 10:11 UTC (History)
0 users

See Also:
Exception Reporter:


Note You need to log in before you can comment on or make changes to this bug.
Description meliandra 2005-08-20 17:42:46 UTC
I'm creating a dialog. In Netbeans I check the box always on top. I couldn't
compile. (Netbeans is running under 1.5 my application is compiled with 1.4.2.)
Then I got a lot of error messages.

This checkbox create code that isn't compatible to older versions. Do I have to
run Netbeans with 1.4? Or what is the solution for this problem?
Comment 1 Tomas Pavek 2005-08-30 13:02:41 UTC
If you need to run on 1.4.2 and know that setAlwaysOnTop is only in 1.5 then
don't set it! ;)

To be sure you can run NB on 1.4.2 - then you'll be offered with 1.4.2
properties only.
Comment 2 Tomas Pavek 2005-08-30 17:11:49 UTC
On our side, we could try to check the target platform of the project the form
is placed in and possibly filter out specific known Swing properties that are
not available on the target platform (supposing the IDE runs on newer version).
Comment 3 Jan Stola 2005-09-27 11:11:34 UTC
We will try to solve this issue in some future release.
Comment 4 Tomas Pavek 2007-08-08 10:11:29 UTC
The palette is already filtered according to the project platform - so component classes that are not available are not
offered (even they are registered in palette content). For the rest we need to check the properties and constants used
as property values or layout constraints. See also issue 99826.

I can see two options how this could look like: either don't show the properties/values in property sheet at all, or
show a warning when a non-existing property/value is used. The latter is easier to implement and less restrictive.