Changeset 246 for trunk/desktop/idl


Ignore:
Timestamp:
Mar 10, 2007, 6:49:44 PM (19 years ago)
Author:
cinc
Message:

Added new method wpConnectDefaultSignalHandlers() to WPFolderWindow.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/desktop/idl/wpfolderwindow.idl

    r245 r246  
    5959
    6060    Default desktop window used by folders to show objects to the user.
     61    It's essential that the WPFolder owning the WPFolderWindow is set
     62    into the instance variable by using wpSetObject() a method inherited
     63    from WPWindow.
     64
     65    This class can be used as a base class for window classes which will
     66    be used for folder windows. When creating a new class override nomInit()
     67    and create your window. Be sure to have at least one container window as
     68    a child of the toplevel window which will hold the folders objects. Save
     69    the handle to this container using wpSetContainerHandle(). Default drag and
     70    drop behaviour for desktop objects can easily be added by calling
     71    wpConnectDefaultSignalHandlers() with the created container handle.
     72
     73    There is no limitation on the number of containers held by the toplevel
     74    window. Each of these containers can be drag and drop enabled for desktop
     75    objects.
     76
    6177
    6278 */
     
    6581  NOMCLASSVERSION(1, 0);
    6682
     83  /**
     84     Query the handle to the container holding the objects.
     85 
     86     \par How to override:
     87     This method is usually not overriden.
     88
     89     \sa wpSetContainerHandle()
     90   */
    6791  PGtkWidget wpQueryContainerHandle();
    68   void wpSetContainerHandle(in PGtkWidget pgWidget);   
    6992
     93  /**
     94     Set the container handle of this folder window into the instance variable.
     95
     96     \remarks Always use this method to save the handle to the folder container.
     97     While it's possible to write to the instance variable from within nomInit()
     98     (where the toplevel window is created with at least one container window as a
     99     child), using this methods gives subclasses the chance to alter the container
     100     by overriding this method.
     101
     102     \param pgWidget Handle to a container window (usually GtkIconView)
     103
     104     \sa wpQueryContainerHandle()
     105   */
     106  void wpSetContainerHandle(in PGtkWidget pgWidget);
     107
     108  /**
     109     Connect signal handlers with the given container which enable drag and drop
     110     of desktop objects and context menus.
     111
     112     \remarks Using this method every container window (don't confuse that with GtkContainer)
     113     can be enabled for drag and drop of desktop objects. Default context menu behaviour
     114     known by desktop object will be enabled, too. There's no limit on the number
     115     of containers in a folder window.
     116
     117     \par How to override:
     118     This method can be overriden if additional signal handlers should be connected to the
     119     container.
     120
     121     \param pgWidget Container window handle. This is for example an icon view.
     122
     123     \sa wpSetContainerHandle()
     124   */ 
     125  void wpConnectDefaultSignalHandlers(in PGtkWidget pgWidget);
     126
     127  /**
     128     Override which creates a toplevel window with a container for icons.
     129   */
    70130  NOMOVERRIDE(nomInit);
    71131
     132  /**
     133     This variable holds the container window handle (normaly a handle of a GtkIconView).
     134
     135     \sa wpSetContainerHandle(), wpQueryContainerHandle()
     136   */
    72137  NOMINSTANCEVAR(PGtkWidget pgContainerHandle);
    73138};
Note: See TracChangeset for help on using the changeset viewer.