Assigning single grid symbol for multiple 3D instruments
Posted: Thu Jul 07, 2016 1:52 pm
I suspect that what i'm looking for isn't possible due to what is considered 'primary key' for the database of symbols, but i thought i'd double-check to make sure.
When looking at drill in grid view, i dislike shapes or letters or etc. because a) it feels cluttered and b) different shapes with no "pinpoint" makes it more difficult to read where exact dots are at a glance. I therefore give all of my performers the same symbol (% which is a dot) and then differentiate sections by color.
However, doing this seems to limit my ability to have 3D view represent actual instruments accurately because in the symbol map, i can't assign a single symbol to multiple classes of people because it appears as if it's not a distinct variable from "keypad stroke". There's a "bug" workaround involving assigning symbols and then reassigning symbols, but it's cumbersome, finicky, and imperfect.
Am i missing something here, or am i correct in my assumptions about this? If true, can the next release of pyware redo database "primary key" to separate "keypad" from "symbol" so that symbols can be redefined for any given keypad stroke?
Is another potential workaround to create my own symbol font map where every "symbol" is the dot and then choose that as my font?
When looking at drill in grid view, i dislike shapes or letters or etc. because a) it feels cluttered and b) different shapes with no "pinpoint" makes it more difficult to read where exact dots are at a glance. I therefore give all of my performers the same symbol (% which is a dot) and then differentiate sections by color.
However, doing this seems to limit my ability to have 3D view represent actual instruments accurately because in the symbol map, i can't assign a single symbol to multiple classes of people because it appears as if it's not a distinct variable from "keypad stroke". There's a "bug" workaround involving assigning symbols and then reassigning symbols, but it's cumbersome, finicky, and imperfect.
Am i missing something here, or am i correct in my assumptions about this? If true, can the next release of pyware redo database "primary key" to separate "keypad" from "symbol" so that symbols can be redefined for any given keypad stroke?
Is another potential workaround to create my own symbol font map where every "symbol" is the dot and then choose that as my font?