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 56328 - viewmodel can't deal with anything but String?
Summary: viewmodel can't deal with anything but String?
Status: CLOSED FIXED
Alias: None
Product: debugger
Classification: Unclassified
Component: Code (show other bugs)
Version: 4.x
Hardware: All All
: P1 blocker (vote)
Assignee: issues@debugger
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-12 22:15 UTC by ivan
Modified: 2006-03-24 13:08 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 ivan 2005-03-12 22:15:21 UTC 
I have a column of type Long and a getValue that returns a Long.
Yet nothing appears in the renderer cell.
When I debug it I end up in this code in TreeNodeModel.getValue():

                        Object value = model.getValueAt (object, id);
                        if ( (value != null) &&
                             (getValueType ().equals (String.class))
                        )
                            properties.put (id, value);
                        firePropertyChange (id, null, value);

So how are non-String values ever supposed to get rendered?
For that matter, isn't fetching all of this through RP awfully slow?
We need to refresh lots of views everytime some state changes in the debugger.
Comment 1 ivan 2005-03-13 22:03:17 UTC 
I ran into this again with my breakpoint enabled Boolean
property. The cell renderer correctly renders a check-box
but while my models getValue returns the correct Boolean, 
as described above it never gets propagated to the cell and the
checkbox stays always in the checked state.

bpt enabledness is pretty basic functionality so 
I'm raising this to a P1.
Comment 2 Jan Jancura 2005-03-22 13:01:49 UTC 
Can you try some new version, please?
This issue should be fixed from 2/2/2005.
Feel free to reopen it in the case of troubles, please.
Comment 3 ivan 2005-03-26 02:01:21 UTC 
OK, it all seems to be working now.
Thanks.