mancurses 0.0.1 → 0.0.2

data/README.md

@@ -14,23 +14,20 @@ Use "/" to search for strings within the page displayed.
 
 Use '?' to see bindings.
 
-When pressing F1 for help or "?" for bindings, and returning, the background is black. You need to 
-press a key for it to refresh. I am figuring this out.
-
 ## General
 
-    This gem is not really gonna make much difference to you. It's faster to just type `man grep` on the 
-    command line and 'q' to get out. It's not like you keep manning pages one after another.
+This gem is not really gonna make much difference to you. It's faster to just type `man grep` on the 
+command line and 'q' to get out. It's not like you keep manning pages one after another.
+
+I am writing this to test out a new text widget which uses a pad. I hope to replace the current
+text widgets such as textview and list and maybe tabular and tree in rbcurse-core with this. 
 
-    I am writing this to test out a new text widget which uses a pad. I hope to replace the current
-    text widgets such as textview and list and maybe tabular and tree in rbcurse-core with this. 
+Currently, using a window requires a lot of work each time one scrolls around. Too much string creation , truncation, sanitizing and gc going on repeatedly. Using a pad simplifies all this.
 
-    Currently, using a window requires a lot of work each time one scrolls around. Too much string creation , truncation, sanitizing and gc going on repeatedly. Using a pad simplifies all this.
+However, pad is not without its issues. If I have two pads on the screen, and a popup is displayed,
+then a black rectangle is left on the other pad. I would have to tab there and scroll for a `prefresh` to happen. Otherwise, the app needs to do some book-keeping of underlying pads created and refresh them when a messagebox or window closes.
 
-    However, pad is not without its issues. If I have two pads on the screen, and a popup is displayed,
-    then a black rectangle is left on the other pad. I would have to tab there and scroll for a `prefresh` to happen. Otherwise, the app needs to do some book-keeping of underlying pads created and refresh them when a messagebox or window closes.
-    
-    If i cannot manage that reliably, then i cannot include this in the main rbcurse-core.
+If i cannot manage that reliably, then i cannot include this in the main rbcurse-core.
 
 ## Contributing
 

data/bin/mancurses

@@ -8,7 +8,7 @@
 #       Author: rkumar http://github.com/rkumar/mancurses/
 #         Date: 2011-11-09 - 16:59
 #      License: Same as Ruby's License (http://www.ruby-lang.org/LICENSE.txt)
-#  Last update: 2013-03-08 01:14
+#  Last update: 2013-03-08 21:03
 #
 #  == CHANGES
 #  == TODO 
@@ -171,6 +171,7 @@ module RubyCurses
     ## 2013-03-07 - 19:57 changed width to @content_cols since data not printing
     # in some cases fully when ansi sequences were present int some line but not in others
     # lines without ansi were printing less by a few chars.
+    # This was prolly copied from rwindow, where it is okay since its for a specific width
     def print(string, _width = @content_cols)
       #return unless visible?
       w = _width == 0? Ncurses.COLS : _width
@@ -239,6 +240,12 @@ module RubyCurses
 
     public
     def repaint
+      ## 2013-03-08 - 21:01 This is the fix to the issue of form callign an event like ? or F1
+      # which throws up a messagebox which leaves a black rect. We have no place to put a refresh
+      # However, form does call repaint for all objects, so we can do a padref here. Otherwise,
+      # it would get rejected. UNfortunately this may happen more often we want, but we never know
+      # when something pops up on the screen.
+      padrefresh unless @repaint_required
       return unless @repaint_required
       if @formatted_text
         $log.debug "XXX:  INSIDE FORMATTED TEXT "
@@ -462,9 +469,10 @@ module RubyCurses
             $log.error " TEXTPAD ERROR INS #{err} "
             $log.debug(err.backtrace.join("\n"))
             textdialog ["Error in TextPad: #{err} ", *err.backtrace], :title => "Exception"
-            # FIXME why does this result in a blank spot on screen till its refreshed again
-            # should not happen if its deleting its panel and doing an update panel
           end
+          ## NOTE if textpad does not handle the event and it goes to form which pops
+          # up a messagebox, then padrefresh does not happen, since control does not 
+          # come back here, so a black rect is left on screen
           return :UNHANDLED if ret == :UNHANDLED
         end
         bounds_check

data/mancurses.gemspec

@@ -4,7 +4,7 @@ $LOAD_PATH.unshift(lib) unless $LOAD_PATH.include?(lib)
 
 Gem::Specification.new do |spec|
   spec.name          = "mancurses"
-  spec.version       = "0.0.1"
+  spec.version       = "0.0.2"
   spec.authors       = ["Rahul Kumar"]
   spec.email         = ["sentinel1879@gmail.com"]
   spec.description   = %q{view manpages in an ncurses window and navigate with vim bindings}

metadata

@@ -1,7 +1,7 @@
 --- !ruby/object:Gem::Specification
 name: mancurses
 version: !ruby/object:Gem::Version
-  version: 0.0.1
+  version: 0.0.2
   prerelease: 
 platform: ruby
 authors:
@@ -9,7 +9,7 @@ authors:
 autorequire: 
 bindir: bin
 cert_chain: []
-date: 2013-03-07 00:00:00.000000000 Z
+date: 2013-03-08 00:00:00.000000000 Z
 dependencies:
 - !ruby/object:Gem::Dependency
   name: bundler
@@ -89,7 +89,7 @@ required_ruby_version: !ruby/object:Gem::Requirement
       version: '0'
       segments:
       - 0
-      hash: -1947742288534939193
+      hash: 2382845020894572024
 required_rubygems_version: !ruby/object:Gem::Requirement
   none: false
   requirements:
@@ -98,7 +98,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
       version: '0'
       segments:
       - 0
-      hash: -1947742288534939193
+      hash: 2382845020894572024
 requirements: []
 rubyforge_project: 
 rubygems_version: 1.8.25