Skip to content

Conversation

@fx-world
Copy link
Contributor

This should enhance compatibility between using RAP und RCP with the same application

Also-by: Ralf Schlesinger [email protected]
Also-by: Rico Scholz [email protected]

In SWT you can execute JavaScript code in the Browser constructor, in
RWT you could not, because the Iframe did not yet exist. Now it flickers
into existence and you can execute JavaScript in it.

Also-by: Ralf Schlesinger <[email protected]>
Adapted test so Browser throws WidgetDisposed, when widget is disposed.

Also-by: Ralf Schlesinger <[email protected]>
It was possible to prevent the delivery of dispose event, by overridding
notifyListeners, this is not possible in swt.

Also-by: Ralf Schlesinger <[email protected]>
Also-by: Ralf Schlesinger <[email protected]>
Also-by: Rico Scholz <[email protected]>
adapted tests to new behavior

Also-by: Ralf Schlesinger <[email protected]>
In SWT the buttons are not in the statemask except in MouseUp.

Also-by: Ralf Schlesinger <[email protected]>
SWT does not call getBackground/getForeground/getFont during
construction, so RWT should not too.

Also-by: Ralf Schlesinger <[email protected]>
RAP is drawing text on coordinate 0,0 everytime at the top. RCP is
stepping down and introduces something like a margin. We set the margins
to get in most cases good looking texts. Could be wrong sometimes and
off by 1.

Also-by: Ralf Schlesinger <[email protected]>
Also-by: Rico Scholz <[email protected]>
@eclipse-rap-bot
Copy link

Can one of the admins verify this patch?

@ifurnadjiev
Copy link
Contributor

ok to test

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants