[Libreoffice-commits] core.git: framework/source odk/examples

[Julien Nabet]

 framework/source/services/frame.cxx                                           |    2 +-
 odk/examples/DevelopersGuide/OfficeDev/DesktopEnvironment/IOnewayLink.java    |    4 ++--
 odk/examples/DevelopersGuide/OfficeDev/DesktopEnvironment/OnewayExecutor.java |    2 +-
 odk/examples/DevelopersGuide/OfficeDev/DesktopEnvironment/StatusListener.java |    2 +-
 4 files changed, 5 insertions(+), 5 deletions(-)

New commits:
commit 5b066bc3efed187dd7e63973d2b9731a9eea31e8
Author: Julien Nabet <serval2412 at yahoo.fr>
Date:   Sun Feb 9 10:14:25 2014 +0100

    Typo: (a)synchronoues -> a(synchronous)
    
    Change-Id: Ia3871d711308eb38ed6e0df81615966cc142030d

diff --git a/framework/source/services/frame.cxx b/framework/source/services/frame.cxx
index 217a096..553979d 100644
--- a/framework/source/services/frame.cxx
+++ b/framework/source/services/frame.cxx
@@ -2667,7 +2667,7 @@ void SAL_CALL Frame::windowDeactivated( const css::lang::EventObject& aEvent ) t
 void SAL_CALL Frame::windowClosing( const css::lang::EventObject& ) throw( css::uno::RuntimeException )
 {
     /* #i62088#
-        Some interceptor objects intercept our "internally asynchronoues implemented" dispatch call.
+        Some interceptor objects intercept our "internally asynchronous implemented" dispatch call.
         And they close this frame directly (means synchronous then).
         Means: Frame::windowClosing()->Frame::close()
         In such situation its not a good idea to hold this transaction count alive .-)
diff --git a/odk/examples/DevelopersGuide/OfficeDev/DesktopEnvironment/IOnewayLink.java b/odk/examples/DevelopersGuide/OfficeDev/DesktopEnvironment/IOnewayLink.java
index 22ce638..33a6b3c 100644
--- a/odk/examples/DevelopersGuide/OfficeDev/DesktopEnvironment/IOnewayLink.java
+++ b/odk/examples/DevelopersGuide/OfficeDev/DesktopEnvironment/IOnewayLink.java
@@ -39,9 +39,9 @@ import java.util.ArrayList;
 /**
  * We need a generic interface to forward any oneway uno interface method
  * by using threads to the original object. Reason:
- * It's not allowed to call synchronoues back to the office if a java object
+ * It's not allowed to call synchronous back to the office if a java object
  * was called in a oneway declared interface method. Then it must be
- * executed asynchronoues. To do so - a thread can be created which use this
+ * executed asynchronous. To do so - a thread can be created which use this
  * interface. It get the object, which whis to be called back and the type and
  * parameter of the original request.
  *
diff --git a/odk/examples/DevelopersGuide/OfficeDev/DesktopEnvironment/OnewayExecutor.java b/odk/examples/DevelopersGuide/OfficeDev/DesktopEnvironment/OnewayExecutor.java
index 355be64..51435cb 100644
--- a/odk/examples/DevelopersGuide/OfficeDev/DesktopEnvironment/OnewayExecutor.java
+++ b/odk/examples/DevelopersGuide/OfficeDev/DesktopEnvironment/OnewayExecutor.java
@@ -37,7 +37,7 @@ import java.util.ArrayList;
 // __________ Implementation __________
 
 /**
- * It's not allowed to call synchronoues back inside an oneway interface call.
+ * It's not allowed to call synchronous back inside an oneway interface call.
  * (see IOnewayLink too). So we start a thread (implemented by this class), which
  * gets all necessary parameters from the original called object and
  * call it back later inside his run() method. So the execution of such oneway call
diff --git a/odk/examples/DevelopersGuide/OfficeDev/DesktopEnvironment/StatusListener.java b/odk/examples/DevelopersGuide/OfficeDev/DesktopEnvironment/StatusListener.java
index 89980b7..29c4fff 100644
--- a/odk/examples/DevelopersGuide/OfficeDev/DesktopEnvironment/StatusListener.java
+++ b/odk/examples/DevelopersGuide/OfficeDev/DesktopEnvironment/StatusListener.java
@@ -57,7 +57,7 @@ import com.sun.star.uno.UnoRuntime;
  * internal holded dispatch object automaticly.
  *
  * Another reason for such extra class for listening:
- * Most listener callbacks are asynchronoues [oneay] requests.
+ * Most listener callbacks are asynchronous [oneay] requests.
  * And it's not allowed to call back synchronously there.
  * So we must start threads for updating something internally.
  *