Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 323899 - DateTimeRidget.setOutputOnly() has no effect
Summary: DateTimeRidget.setOutputOnly() has no effect
Status: RESOLVED FIXED
Alias: None
Product: Riena
Classification: RT
Component: ridget (show other bugs)
Version: unspecified   Edit
Hardware: Other All
: P3 normal (vote)
Target Milestone: 3.0.0.M2   Edit
Assignee: Elias Volanakis CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-08-29 01:24 EDT by Patrick He CLA
Modified: 2010-10-29 06:19 EDT (History)
1 user (show)

See Also:

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 Patrick He CLA 2010-08-29 01:24:34 EDT 
Build Identifier: 

When DateTimeRidget.setOutputOnly(true) is called, the ridget still can change the value of itself and the model.

Reproducible: Always

Steps to Reproduce:
1. Open DateTimeSubModuleController in SWT example application
2. Add dtDate.setOutputOnly(true); or to any DateTimeRidget
3. Run the example application. The date is still selectable and changeable. Also models can be updated too.
Comment 1 Elias Volanakis CLA 2010-08-30 16:48:51 EDT 
Thanks, resolved in HEAD.

As a workaround: since output-only is equivalent to enabled:=false you can use ridget.setEnabled(false) instead (only for the DateTimeRidget).