Bc2000 (for the BCF2000 & BCR2000)

Hi Mark-

I have noticed the problem with the fixed-width columns also --
there's no way to drag them out to see the full text.

I can't say I've seen too many problems otherwise, but don't bother
too much about it. I can always switch the DPI back to normal for the
BC Manager. I mostly use the PC in question for SONAR or REAPER, and
sometimes for Firefox. I went to 115% because my eyes aren't what they
used to be!:) I'm glad you can confirm what I saw, though!

Thanks-

-Susan

--- In bc2000@yahoogroups.com, "Mark van den Berg" <markwinvdb@...> wrote:
>
> --- In bc2000@yahoogroups.com, "hooeygoo" <SMG_Music@> wrote:
> > Ah! I only have 3 knobs in the standard output tab. It's probably
> > because I'm using a Custom DPI setting (115% of normal). The one I'm
> > missing is "Controller", oddly enough! ;) 
> 
> This is REALLY weird, Susan!
> 
> > I'll change the DPI setting, bet that'll do it.
> 
> You're right: the problem is indeed your 115% DPI setting. I've tested
> this setting myself and found the same problem. NORMALLY there is a
> row of FOUR knobs: Channel, Controller, Value 1 and Value 2, but in
> your situation (for a reason I don't understand yet) Value 1 and Value
> 2 are shifted one item to the left; so Value 1 simply overlays
Controller.
> 
> In fact, you CAN actually select the invisible Controller knob, namely
> by selecting the Channel knob, then pressing the Tab key: if you then
> press the left/right arrows, the text string below changes
> accordingly! (This indicates the name of the current controller
> value.) But of course this isn't workable.
> 
> I've noticed that your 115% mode also causes some other strange effects:
> - Certain knobs are smaller than others (e.g. Value 1 vs. Value 2).
> - The text strings in tables sometimes extend beyond their column
> widths; this is especially annoying for columns with fixed widths,
> such as the first 3 in the button and encoder list windows. ("Normal"
> columns can be narrowed/widened by dragging the splitter in the header
> row.)
> 
> I'll try to figure out the exact hows and whys of all these problems.
> I MIGHT be able to come up with a solution (perhaps even in the
> upcoming vs. 1.6.0), but I'm not very hopeful. I painstakingly made
> sure that everything fits perfectly under a standard DPI setting, but
> I hadn't realized how bad things can go wrong under non-standard
settings.
> 
> Have you seen this type of problem with other software under your 115%
> mode?
> I seem to remember that several years ago I myself tried a different
> DPI setting (125% I think), but I went back to standard mode almost
> immediately in disgust, because of all kinds of problems with various
> programs.
> 
> Mark.
>