From d80ad003f2084eb687102c957be5a166c2b639cf Mon Sep 17 00:00:00 2001 From: Randy Rohrbach Date: Mon, 17 Nov 2008 19:49:57 +0000 Subject: [PATCH] Bugzilla 255550 --- .../ui/memory/transport/SRecordExporter.java | 17 ++++++++++++++++- 1 file changed, 16 insertions(+), 1 deletion(-) diff --git a/plugins/org.eclipse.dd.debug.ui.memory.transport/src/org/eclipse/dd/debug/ui/memory/transport/SRecordExporter.java b/plugins/org.eclipse.dd.debug.ui.memory.transport/src/org/eclipse/dd/debug/ui/memory/transport/SRecordExporter.java index 9f13f1be043..689c4ecdcb0 100644 --- a/plugins/org.eclipse.dd.debug.ui.memory.transport/src/org/eclipse/dd/debug/ui/memory/transport/SRecordExporter.java +++ b/plugins/org.eclipse.dd.debug.ui.memory.transport/src/org/eclipse/dd/debug/ui/memory/transport/SRecordExporter.java @@ -301,6 +301,22 @@ public class SRecordExporter implements IMemoryExporter }); composite.pack(); + parent.pack(); + + /* + * We need to perform a validation. If we do it immediately we will get an exception + * because things are not totally setup. So we schedule an immediate running of the + * validation. For a very brief time the view logically may show a state which does + * not reflect the true state of affairs. But the validate immediately corrects the + * info. In practice the user never sees the invalid state displayed, because of the + * speed of the draw of the dialog. + */ + Display.getDefault().asyncExec(new Runnable(){ + public void run() + { + validate(); + } + }); return composite; } @@ -364,7 +380,6 @@ public class SRecordExporter implements IMemoryExporter } fParentDialog.setValid(isValid); - }