Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Possibility to have effect per row
#10
(12-23-2020, 07:24 PM)mvdirty Wrote: Just a quick note: Of the three places in the manual where PROW is documented, only one of them (in the CV16 section) mentions that the last FX column is excluded. If this is true for all cases then it might be worth copy/pasting that over into the other two during the next manual update.

Related to this comment, as a new user I'm often using ctrl+f to find keywords in the manual (note that I have already read it once from front to back). Although the manual is well organized and detailed, I often end up jumping into a section of text that is pertinent to one of the expanders, which can lead to confusion if the detail does not translate exactly to what a vanilla NerdSEQ user experiences. One has to scroll up, sometimes several pages, to see if the section is expander-specific.

I'm sure that there are conscious choices that have been made in organizing the manual that I haven't considered, but a constructive suggestion is 1) to completely remove expander details/descriptions into separate documents so that a vanilla NerdSEQ user is not overwhelmed by particulars of expanders that they do not own; or, 2) To place expander-specific details on some combination of a coloured background, different font, font colour etc... so that it's clear that bodies of text are specific to an expander.
Reply


Messages In This Thread
Possibility to have effect per row - by Cedre - 09-30-2020, 09:34 PM
RE: Possibility to have effect per row - by Cedre - 09-30-2020, 10:09 PM
RE: Possibility to have effect per row - by TME - 12-23-2020, 02:54 PM
RE: Possibility to have effect per row - by Cedre - 10-01-2020, 07:09 PM
RE: Possibility to have effect per row - by TME - 12-23-2020, 04:12 PM
RE: Possibility to have effect per row - by TME - 12-24-2020, 03:37 PM
RE: Possibility to have effect per row - by TME - 12-24-2020, 04:19 PM

Forum Jump:


Users browsing this thread: 1 Guest(s)