golly-test Mailing List for Golly

Okay, I've checked in a Lua version of the old change-state.py, with a
few adjustments that I hope are improvements.

Have posted an explanation of some of the details here:

  http://conwaylife.com/forums/viewtopic.php?p=81875#p81875

I should have added a comment like the ones in toLife.lua and
toLifeHistory.lua, like

"--   intended to be mapped to a keyboard shortcut, e.g., Alt+K"

Will put that line in along with any other updates that turn out to be
a good idea.

Keep the cheer,


Dave

On Tue, Aug 20, 2019 at 6:48 PM Tomas Rokicki <ro...@gm...> wrote:
>
> I also like it, and frankly I'm happy to get it!  Thanks, Dave!
>
> On Tue, Aug 20, 2019 at 4:47 PM Andrew Trevorrow <an...@tr...> wrote:
>>
>> Dave:
>>
>> > Meanwhile, this evening I spent an hour merging the good points of
>> > change-state.py and toChangeColors.py.  So far I've ended up with the
>> > following.  I'd be curious as to whether a port of this would be
>> > welcome in the Lua folder under the name "toChangeColor.lua", maybe
>> > with an Alt+K keyboard shortcut.
>>
>> Sounds fine to me.
>>
>> Andrew
>>
>>
>> _______________________________________________
>> Golly-test mailing list
>> Gol...@li...
>> https://lists.sourceforge.net/lists/listinfo/golly-test
>
>
>
> --
> --  http://cube20.org/  --  http://golly.sf.net/  --
> _______________________________________________
> Golly-test mailing list
> Gol...@li...
> https://lists.sourceforge.net/lists/listinfo/golly-test

I also like it, and frankly I'm happy to get it!  Thanks, Dave!

On Tue, Aug 20, 2019 at 4:47 PM Andrew Trevorrow <an...@tr...>
wrote:

> Dave:
>
> > Meanwhile, this evening I spent an hour merging the good points of
> > change-state.py and toChangeColors.py.  So far I've ended up with the
> > following.  I'd be curious as to whether a port of this would be
> > welcome in the Lua folder under the name "toChangeColor.lua", maybe
> > with an Alt+K keyboard shortcut.
>
> Sounds fine to me.
>
> Andrew
>
>
> _______________________________________________
> Golly-test mailing list
> Gol...@li...
> https://lists.sourceforge.net/lists/listinfo/golly-test
>


-- 
--  http://cube20.org/  --  http://golly.sf.net/  --

Dave:

> Meanwhile, this evening I spent an hour merging the good points of
> change-state.py and toChangeColors.py.  So far I've ended up with the
> following.  I'd be curious as to whether a port of this would be
> welcome in the Lua folder under the name "toChangeColor.lua", maybe
> with an Alt+K keyboard shortcut.

Sounds fine to me.

Andrew

For years now I've been posting links to a Python script that I always
keep handy myself for editing purposes, toChangeColors.py:

  http://conwaylife.com/forums/viewtopic.php?p=14742#p14742

That was basically my version of change-state.py in Golly's online
scripts database.  It's a lot faster than change-state.py, because it
iterates through lists of non-zero cells instead of doing a getcell()
on every cell in the chosen bounding box.

Of course that means that it can't change state-0 cells to some other
state.  For me that's okay -- I mainly use toChangeColors.py for
changing LifeHistory state-2 blue envelope cells to state 0, and
changing state-1 labels to state 4

A couple of Golly versions back I started working on a super-fast
version of the toChangeColors script.  If you were operating on an
entire pattern rather than a selection, it would write out a custom
rule to do the state change in one fell swoop -- no iterating through
cells at all.  I think I still have that script around somewhere,
pretty much in working order.  It just needed some user-friendly
error-checking, and then a port to Lua.

But I'm no longer terribly interested in it.  It seems to be pretty
rare that color changes are needed on huge patterns, and most people
working with such huge patterns can also write a one-off rule script
in a minute or two to solve specific color-change requirements...
Maybe we could put a toChangeColorsQuick.lua into the online scripts
database, if a good user-friendly version ever shows up.

Meanwhile, this evening I spent an hour merging the good points of
change-state.py and toChangeColors.py.  So far I've ended up with the
following.  I'd be curious as to whether a port of this would be
welcome in the Lua folder under the name "toChangeColor.lua", maybe
with an Alt+K keyboard shortcut.

It seems to me that easy bulk color changing is a big missing piece of
functionality in Golly, and change-state.py just doesn't seem
convenient enough enough any more... especially nowadays when the
number of Lua-only Golly installs might be gradually on the rise.

Votes in favor? Votes against?  I can get the remaining TODOs done
pretty quick, but if the rest of the Golly Gang thinks it's a lousy
idea anyway, I might invest the time elsewhere.

Keep the cheer,


Dave


# toChangeColor.py/.lua
# Switch all cells of a clicked-on color in the selected pattern to
the current brush color
# TODO:  Convert this Python script to Lua
# TODO:  Set the current drawing color to whatever is saved in (file
equivalent to shift.ini -- toChangeColor.ini)
#        This way the utility can be preset as a single-purpose
change-to-0 script
#           (if its primary use will be to get rid of LifeHistory cells)
#        but it can still be reconfigured by changing the drawing
state while the script is running,
#        and that change would then stick until the next time the tool is used.
# TODO:  Assign a shortcut key?  Alt+K would put it in line with Alt+H
and alt+J tools,
#        allowing toChangeColor.lua to be used to (K)ill state-2 cells
in a LifeHistory pattern
#        without affecting states 3 through 6 in the way that an
Alt+J, Alt+H cycle does.

import golly as g
from time import time

limits = "selection"
seltype = " selected"
r = g.getselrect()
if len(r)==0:
  limits = "pattern's bounding box"
  seltype = ""
  r = g.getrect()
  if len(r)==0:
    g.exit("No pattern to change.")

# set fill limits to the chosen rectangle
minx, miny, sizex, sizey = r
maxx = minx + sizex
maxy = miny + sizey

area = g.getcells(r)
if len(area)%2 == 0:
  g.exit("Nothing to do here -- rule is not multistate.")
newstate = g.getoption("drawingstate")
oldstate = newstate

# wait for user to click a cell
g.show("Click a cell to change all" + seltype + " cells of that state
to current drawing state, "
       + str(newstate) + ", or Esc to cancel.")
while 1:
   event = g.getevent()
   # user may change drawing state at any time
   newstate = g.getoption("drawingstate")
   if newstate != oldstate:
      g.show("Click a cell to change all" + seltype + " cells of that
state to current drawing state, "
              + str(newstate) + ", or Esc to cancel.")
      oldstate = newstate

   if event.startswith("click"):
      # event is a string like "click 10 20 left none"
      evt, xstr, ystr, button, mods = event.split()
      x = int(xstr)
      y = int(ystr)
      if x < minx or x >= maxx or y < miny or y >= maxy:
         g.warn("Click inside the " + limits + ".")
      else:
         oldstate = g.getcell(x, y)
         if oldstate == newstate:
            g.warn("The clicked cell must have a different state\n"+
                   "from the current drawing state, " + str(newstate) + ".")
         else:
            break
   else:
      g.doevent(event)

# tell Golly to handle all further keyboard/mouse events
g.getevent(False)

if oldstate == 0:
   changed = 0
   total = float(sizex) * float(sizey)
   oldsecs = time()
   for row in xrange(miny, maxy):
      # might be large pattern so show percentage done each second
      newsecs = time()
      if newsecs - oldsecs >= 1.0:
         oldsecs = newsecs
         g.show("Changing cell states: " +
                str(int(100 * (row - miny) * sizex / total)) + "%")
         g.update()

      # allow keyboard interaction
      g.dokey( g.getkey() )

      for col in xrange(minx, maxx):
         if g.getcell(col, row) == oldstate:
            g.setcell(col, row, newstate)
         changed += 1
else:
   oldsecs = time()
   numcellsx3 = len(area)
   count = 0
   for i in range(0,len(area)-2,3):
      # might be large pattern so show percentage done each second
      newsecs = time()
      if newsecs - oldsecs >= 1.0:
         oldsecs = newsecs
         g.show("Changing cell states: " + str(int(100 * i / numcellsx3)) + "%")
         g.update()
      if area[i+2]==oldstate:
         g.setcell(area[i],area[i+1],newstate)
         count +=1
      # allow keyboard interaction
      g.dokey( g.getkey() )
   g.show("Changed " + str(count) + " cells to state " + str(newstate) + ".")