| Summary: | [ToolTip] Visibility does not work as in SWT | ||
|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Tim Buschtoens <tbuschto> |
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | tbuschto |
| Version: | 1.4 | ||
| Target Milestone: | 1.4 M5 | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
Thanks for the hint, Tim. You guessed right, setting the default visibility to false did it. Changes are in HEAD I'm sorry, but it seems the push-button scenario described above still doesn't work. The tooltip can appear exactly once. Also, you did not run the jsCompressor, so the changes were not visible in the non-debug variant. Reopend bug. I overlooked that there are two issues. Sorry for not geting this right in the first place. It should work now. client.js is rebuilt, changes are in HEAD Works fine now. |
Run the follwing in SWT and RAP: --- public int createUI() { Display display = new Display(); Shell shell = new Shell( display, SWT.TITLE | SWT.CLOSE ); shell.setLayout( new GridLayout( 1, false ) ); Button button = new Button( shell, SWT.PUSH ); button.setText( "push" ); final ToolTip tooltip = new ToolTip( shell, SWT.NONE ); tooltip.setMessage( "foo" ); tooltip.setText( "bar" ); tooltip.setLocation( 200, 200 ); button.addSelectionListener( new SelectionAdapter() { public void widgetSelected(SelectionEvent e) { tooltip.setVisible( true ); } } ); shell.layout(); shell.open(); while (!shell.isDisposed()) { if (!display.readAndDispatch()) { display.sleep(); } } return 0; } --- SWT: ToolTip is not visible at first. Its shown when pushing the button, stays for a few seconds, then fades. Pushing the button again and the tooltip appears again. RAP: ToolTip can be shortly seen fading out when the application starts. Its shown when pushing the button, stays for a few seconds, then fades, just like in SWT. Pushing the button again does nothing. Not sure why pushing the button again doesnt work, might be a server-side issue. The animation at application start can probably be prevented by setting the default value of the client-property "visibility" to false. (An educated guess.)