Rational Developer for Power Systems Software
V7.6

com.ibm.etools.iseries.remotebuild.util
Class MessageDialogUtil

java.lang.Object
  extended by com.ibm.etools.iseries.remotebuild.util.MessageDialogUtil

public class MessageDialogUtil
extends Object


Constructor Summary
MessageDialogUtil()
           
 
Method Summary
static boolean showStatus(Shell shell, RBStatus status)
          Shows a status message and asks whether to cancel the operation.
static boolean showSystemMessage(Shell shell, SystemMessage message)
          Shows a system message in a standard system message dialog.
 
Methods inherited from class java.lang.Object
clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait
 

Constructor Detail

MessageDialogUtil

public MessageDialogUtil()
Method Detail

showStatus

public static boolean showStatus(Shell shell,
                                 RBStatus status)
Shows a status message and asks whether to cancel the operation.

Returns:
true if the operation in progress should continue, false if the operation should be canceled.

showSystemMessage

public static boolean showSystemMessage(Shell shell,
                                        SystemMessage message)
Shows a system message in a standard system message dialog.

Parameters:
message - the SystemMessage to show. If the message is null, this does nothing.
Returns:
true if the dialog indicates that the operation in progress should continue. false if the operation should be canceled. If the message is an inquiry message, it is assumed to ask the question "Do you want to continue?". If Yes is pressed the operation is continued. If NO is pressed or the dialog is canceled, the operation should also be canceled.

Rational Developer for Power Systems Software
V7.6

Copyright 2011 IBM Corp. All Rights Reserved.

Note: This documentation is for part of an interim API that is still under development and expected to change significantly before reaching stability. It is being made available at this early stage to solicit feedback from pioneering adopters on the understanding that any code that uses this API will almost certainly be broken (repeatedly) as the API evolves.