dhowe / relc3 Goto Github PK

This has come up before; I've tried various things but I think it's one for you: when the app starts or when we load a new text, we want to set at least one reader to .setGridPosition(0,0) or .setCurrentCell(verso.cellAt(0,0) but these trigger an unwanted page turn. I've done a workaround using an OK_TO_FOCUS flag in MachineReader and this seems to work but isn't there a better way?

lines 1412 to 1428 - looks like you were going to have a way to stop/complete all fading behaviors on a grids RiTexts, but did write one, such that reset(true) would have done this. Wouldn't this be pretty easy for you? Hope so.

I've had a go at this and the current traces of my attempts are commented out on line 407 of ELC3Multi in its draw method.
When this line is not commented out, the readerSpeed (in seconds) seems to be ignored or changed by ? MachineReader and it is not clear whether the adjustment is working (even when very exaggerated).
Would be nice to make this work but I think it needs your skills ...

A perigram reader is this initial default and so, on launch, the 'Spawning' button should be invisible or - I'd prefer this I think - greyed out.

• run sketch
• switch to "Less Directed Perigram"
• try to change the reader color with the color button
  No effect. But when you switch to another reader and change color it will change color (already has?)
  I had a look at this but couldn't work it out on a first pass anyway.

sketch halts with no report if you click the button to change readers while a page is flipping/turning

Need to add the downloadable executables to this page: http://thereadersproject.org/elc3.html#ELC3
and do minor redesign/text-updates (should also add the instructions from the rtf)

https://github.com/dhowe/RELC3/tree/Readers2016_asPosted/applications

any reason not to use menus (which show the actual options), rather than buttons which force the user to only choose the next option (which is a mystery)?

thoughts?

now that the interface is almost sorted out, would it be better to leave the reader as currently selected and configured when changing texts? If you agree: yes, then assign to me.

• change 'Text' button to 'Title'
• add 'Text' button with options: grey (more white than currently), dim (as now), dark (= invisible)

... so that (try the mesostic reader) no highlighted words=letters are ever missed?

do this:

• start sketch;
• switch to Mesostic Jumper and set speed to Fluent
• let the reader turn the page and note that all the letters of the Mesostic phrase are showing (fixed this before the exitWord VBs would have run before the page finished flipping, but to get the first mesostic word on the new page to highlight, ihave taken special measure).

This first time round the visual behaviors play nice. Now, continue thus:

• switch to a Perigram reader and make it Fast;
• let it turn a page;
• switch back to the Mesostic Jumper at Fluent or Steady;
• let it turn a page.

Notice that the first mesostic word on the new page is highlighted but then suddenly and too quickly 'switches off' (revert to grid default colors) This only happens after having selected readers with other visuals. I think it is something to do with the way fades are handled and this is one of your Deep Mysteries.

sure, though it probably makes sense to simply load the texts once in the beginning... (or is that what you mean?)

Not sure if this is expected behavior, but if so, it should have a better name than 'dying'
Note that this is not new, but only brought to light because of your log message for null words in Machine Reader.draw()

[WARN] wordBeingRead is null at this point in [email protected]()
trp.reader.SimpleReader@2eb90014  -> RiText['obliterated']
Died with null cell ahead to the N from: RiText['Placed?']
[WARN] wordBeingRead is null at this point in [email protected]()
Died with null cell ahead to the S from: RiText['in']
[WARN] wordBeingRead is null at this point in [email protected]()
Died with null cell ahead to the NE from: RiText['Having']
[WARN] wordBeingRead is null at this point in [email protected]()
Died with null cell ahead to the NE from: RiText['my']
[WARN] wordBeingRead is null at this point in [email protected]()
trp.reader.SimpleReader@2eb90014  -> RiText['that']
Died with null cell ahead to the SW from: RiText['it']

To help the user to know that there is a bottom control bar, maybe we could have it appear for a few second when the programme starts, then we can just let it disappear and only shows up when hover like right now.

If a new reader (def: simple spawner or perigram spawner) has been switched to and then the user tries to click-switch to the next text, crash with this:
[ERROR] Illegal state in RiTextGrid.getGridFor(), no grid for RiText: RiText['']
java.lang.RuntimeException
[FATAL] Illegal state in RiTextGrid.getGridFor(), no grid for RiText: RiText['']

... yet for our sketch. See note associated with the relevant commit.

since there can be an odd number of half-black-space lines on either right or left grid currently, the position of a bottom line for this text can vary. I had to adjust the bottom margin of the layout in order to make all pages work with The Image and the bottom control bar. Daniel: you may want to make blank lines in The Image full blank lines and see if this looks better to you.

i.e. when the grids being displayed have do not have the reader on them. The page turns/flips for no reason. Shouldn't happen.

• halo but make the tendrils display properly, for spawners
• halo with the mesostic letter in caps, for m.j.