README.org in fxruby-enhancement-0.0.3 vs README.org in fxruby-enhancement-0.0.4

@@ -358,10 +358,29 @@
      respecively.
 
      You may declare your ingress_handler anywhere in your code and have 
      the expected happen.
 
+     igress_handler may also be specified with more than one tag, for
+     instance:
+     #+begin_src ruby
+     ingress_handler :warn, :info, :error do |type, log|
+       case type
+       when :warn
+         ...
+       when :info
+         ...
+       when :error
+         ...
+       else
+         raise "Unknown log type"
+       end
+     end
+     #+end_src
+
+     The same block is assigned to all the given tags of :warn, :info, and :error.
+
 **** TODO deferred_setup
 **** TODO Mapping between fx_* declarations and the FX* FXRuby objects
 **** binding.fx   
      This is a way to split up your layouts into different .fx "modules", purely for
      organizational reasons. For example,
@@ -870,9 +889,10 @@
 ** Release Notes
    | Version |       Date | Notes                                                   |
    |---------+------------+---------------------------------------------------------|
    |   0.0.2 | 2017-01-11 | Initial release                                         |
    |   0.0.3 | 2017-01-15 | Needed to require fox16/colors for FXColor to be loaded |
+   |   0.0.4 | 2017-01-16 | ingress_handler now handles multiple tags.              |
 
 ** Known Issues
    | Version |       Date | Issues                                                |
    |---------+------------+-------------------------------------------------------|
    |   0.0.2 | 2017-01-11 | Not enough example code!!! Need more documentation!!! |