Documentation/Source/eric5.DebugClients.Python.DebugClientThreads.html

changeset 945
8cd4d08fa9f6
parent 440
69ace3e2dcf6
child 1228
7afaf2fca55b
diff -r 1b59c4ba121e -r 8cd4d08fa9f6 Documentation/Source/eric5.DebugClients.Python.DebugClientThreads.html
--- a/Documentation/Source/eric5.DebugClients.Python.DebugClientThreads.html	Fri Mar 11 08:55:14 2011 +0100
+++ b/Documentation/Source/eric5.DebugClients.Python.DebugClientThreads.html	Fri Mar 11 16:51:57 2011 +0100
@@ -92,11 +92,11 @@
         Constructor
 </p><a NAME="DebugClientThreads.attachThread" ID="DebugClientThreads.attachThread"></a>
 <h4>DebugClientThreads.attachThread</h4>
-<b>attachThread</b>(<i>target = None, args = None, kwargs = None, mainThread = 0</i>)
+<b>attachThread</b>(<i>target=None, args=None, kwargs=None, mainThread=0</i>)
 <p>
         Public method to setup a thread for DebugClient to debug.
 </p><p>
-        If mainThread is non-zero, then we are attaching to the already 
+        If mainThread is non-zero, then we are attaching to the already
         started mainthread of the app and the rest of the args are ignored.
 </p><dl>
 <dt><i>target</i></dt>
@@ -120,7 +120,7 @@
 </dd>
 </dl><a NAME="DebugClientThreads.eventLoop" ID="DebugClientThreads.eventLoop"></a>
 <h4>DebugClientThreads.eventLoop</h4>
-<b>eventLoop</b>(<i>disablePolling = False</i>)
+<b>eventLoop</b>(<i>disablePolling=False</i>)
 <p>
         Public method implementing our event loop.
 </p><dl>
@@ -131,7 +131,7 @@
 </dd>
 </dl><a NAME="DebugClientThreads.lockClient" ID="DebugClientThreads.lockClient"></a>
 <h4>DebugClientThreads.lockClient</h4>
-<b>lockClient</b>(<i>blocking = 1</i>)
+<b>lockClient</b>(<i>blocking=1</i>)
 <p>
         Public method to acquire the lock for this client.
 </p><dl>
@@ -183,14 +183,14 @@
 <p>
     Module function used to allow for debugging of multiple threads.
 </p><p>
-    The way it works is that below, we reset thread._start_new_thread to 
+    The way it works is that below, we reset thread._start_new_thread to
     this function object. Thus, providing a hook for us to see when
-    threads are started. From here we forward the request onto the 
+    threads are started. From here we forward the request onto the
     DebugClient which will create a DebugThread object to allow tracing
     of the thread then start up the thread. These actions are always
     performed in order to allow dropping into debug mode.
 </p><p>
-    See DebugClientThreads.attachThread and DebugThread.DebugThread in 
+    See DebugClientThreads.attachThread and DebugThread.DebugThread in
     DebugThread.py
 </p><dl>
 <dt><i>target</i></dt>

eric ide

mercurial