[Gridflow-cvs] [svn] commit: r4365 - in /trunk/doc: flow_classes/#io.x11-help.pd format.xml

gridflow-cvs at artengine.ca gridflow-cvs at artengine.ca
Sat Oct 24 19:36:50 EDT 2009


Author: matju
Date: Sat Oct 24 19:36:49 2009
New Revision: 4365

Log:
partial help for [#out x11]

Added:
    trunk/doc/flow_classes/#io.x11-help.pd
Modified:
    trunk/doc/format.xml

Modified: trunk/doc/format.xml
==============================================================================
--- trunk/doc/format.xml (original)
+++ trunk/doc/format.xml Sat Oct 24 19:36:49 2009
@@ -375,19 +375,19 @@
 		conventions for dealing with them:
 
 		<method name="endian" type="symbol(big|endian|same)">
-			<list><li>big:
+			<list>big:
 			A number will be written starting with the biggest digit.
 			This is the natural way on the Macintosh, Sun, Amiga, and so on.
-			</li>
-			<li>little:
+			
+			little:
 			A number will be written starting with the smallest digit.
 			This is the natural way on the Intel 386/Pentium.
-			</li>
-			<li>same:
+			
+			same:
 			A number will be written in whichever way is more natural
 			on this computer. The natural way is slightly faster to handle.
 			This is the default setting.
-			</li>
+			
 			</list>
 		</method>
 		
@@ -442,13 +442,13 @@
 			<arg type="symbol(read|mmap)"/>
 			<arg type="integer" default="2"/>
 			<list>
-			<li>mmap:
+			mmap:
 			This is the normal (and fast) way of transferring pictures
 			from the camera.
-			</li>
-			<li>read:
+			
+			read:
 			Some cameras/drivers only support this instead of mmap.
-			</li></list>
+			</list>
 			In case of mmap, the extra numeric argument sets the
 			queue length in number of frames, so you can select an
 			appropriate tradeoff between efficiency and latency.
@@ -469,154 +469,6 @@
 		
 	</class>
 </section>
-
-<section name="Window Output">
-
-	<class name="format x11 #in/#out">
-		supports 15,16,24,32-bit truecolor displays
-
-		now also support 8-bit indexed displays, using a private colormap
-		configured as 3:3:2 RGB. When using 8-bit you can specify the
-		"use_stripes" option to use a completely different color scheme
-		involving R,G,B diagonal stripes, a kind of 6:6:6 RGB spread over three
-		pixels.
-
-		If you are using Windows or MacOS 10: you will have to install
-		a X11 server. This will emulate Unix display on your OS. (note:
-		Unix systems also need a X11 server, but it's built-in and handles
-		the video driver directly). In the case of MacOS 10 and QNX that both
-		use non-X11 display technology on top of a basically Unix OS, the
-		OS comes with a X11 server, but it may be on a "bundled software"
-		CD.
-	
-		<method name="open x11">
-			synonym of "open x11 here".
-		</method>
-
-		<method name="open x11 here">
-			connects to the default X11 server,
-			according to your environment variable "DISPLAY".
-		</method>
-
-		<method name="open x11 local">
-			<arg name="display_number" type="integer"/>
-			connects to a display server on this machine.
-		</method>
-		
-		<method name="open x11 remote">
-			<arg name="host_name" type="symbol"/>
-			<arg name="display_number" type="integer"/>
-			connects to a remote X11 display server using TCP.
-			Sorry, IP addresses are not supported.
-			Port number will be 6000 plus the display number, because
-			of the X11 standard.
-		</method>
-		
-		<method name="grid">
-			<arg name="grid" type="grid(rows columns {red green blue})"/>
-			resizes the window to the size of the grid;
-			encodes that grid in the display's pixel format;
-			also displays it if autodraw &gt; 0
-			the values must be in range 0-255,
-			or else they will be "wrapped".
-		</method>
-
-		
-		Destroying the object (or sending "close") should close the window.
-		
-
-		because of the design of Xlib, or if any of the connections
-		involved crashes, then the whole program has to be terminated.
-		(don't you love xlib). Something similar happens if you close any
-		of the windows yourself, but IIRC this could be fixed.
-
-		only one window may be used per connection (to simplify matters;
-		this doesn't reduce flexibility).
-
-		there is an additional argument that may be added to every
-		"open" message; if you don't put it, a new toplevel window is created.
-		if you put "root" then the screen's wallpaper will be used instead
-		(it may fail to work with some popular window managers). You can also
-		put a window number, e.g. 0x28003ff, you may connect to
-		an existing window; you can find out the number of a window by using
-		a tool like xwininfo, part of X11 standard tools.
-
-		<method name="out_size">
-			<arg name="height" type="integer"/>
-			<arg name="width"  type="integer"/>
-			changes the window's size, just like sending a grid
-			dim(height,width,3) would.
-
-			this affects the size of screen captures too.
-		</method>
-
-		<method name="setcursor">
-			<arg name="cursor" type="0..63"/>
-			Selects one of the 64 predefined cursors of X11. (Note that if
-			your cursor table has them numbered from 0 to 126 using only even
-			numbers, then those cursor numbers are all doubled compared to
-			the ones GridFlow uses.)
-		</method>
-		
-		<method name="hidecursor">
-			This makes the cursor invisible.
-		</method>
-
-		<outlet id="0">
-			<method name="position">
-				<arg name="y" type="integer"/>
-				<arg name="x" type="integer"/>
-				<arg name="buttons" type="integer"/>
-				
-				This is emitted every time the cursor moves inside
-				the window connected to this format handler. This is also
-				emitted when the cursor is dragging from inside to outside
-				the window. This is also emitted when a mouse button is pressed.
-
-				The y and x coordinates are relative to the upper
-				right corner of the window. Specific button states may be
-				extracted from the button value by applying [&gt;&gt;
-				buttonnumber] and then checking whether the result is odd.
-				Button numbers normally are:
-				<list start="0">
-				<li>Shift</li>
-				<li>CapsLock</li>
-				<li>Control</li>
-				<li>Alternate</li>
-				<li>NumLock</li>
-				<li>???</li>
-				<li>Meta</li>
-				<li>ScrollLock</li>
-				<li>Left Button</li>
-				<li>Middle Button</li>
-				<li>Right Button</li>
-				<li>Wheel Up</li>
-				<li>Wheel Down</li>
-				</list>
-				NOTE: This message form may become longer in the future, but the already defined parts will stay the same.
-			</method>
-			<method name="keypress">
-				<arg name="y" type="integer"/>
-				<arg name="x" type="integer"/>
-				<arg name="buttons" type="integer"/>
-				<arg name="keyname" type="symbol"/>
-				Similar to position above, but this is emitted when a
-				keyboard key is pressed while this format handler's window
-				is active. Keynames follow the X11 standard, similarly to PureData's [keyname] object.
-				The only exception is that keynames that are digits get prefixed by a capital D so that
-				they don't get mistaken for actual numbers.
-				NOTE: This message form may become longer in the future, but the already defined parts will stay the same.
-			</method>
-			<method name="keyrelease">
-				<arg name="y" type="integer"/>
-				<arg name="x" type="integer"/>
-				<arg name="buttons" type="integer"/>
-				<arg name="keyname" type="symbol"/>
-				Same as keypress but when a key gets released instead.
-				NOTE: This message form may become longer in the future, but the already defined parts will stay the same.
-			</method>
-		</outlet>
-	</class>
 
 	<class name="format quartz #out">
 		The equivalent of format x11 on MacOS 10.x, but with less features (sorry).



More information about the Gridflow-cvs mailing list