Hello fredvs, you wrote on Fri, 3 Apr 2020 14:51:29 -0700 (MST):
> > I'll rebuild all of my "private" utilities > > Nice, it will be welcome. > And dont forget to create a GitHub account! Won't be warranted for that few pieces of code crap. I'll put'em on my web site again and send you a notice about it. But, BTW, I got a couple "gripes" (bemol, as you like to name it). - At least here in Europe, AFAIK, by convention the color "red" means something like "danger", "problem", "failure", while a mere warning is expressed by the color "yellow". In mseide, this color assignment is switched: warnings are marked "red", while errors are flagged "yellow". This made me uneasy every time when it newly occurred. Of course, it can be easily configured to the "normal" way. But - if our Asian friends here won't oppose (as they don't neccessarily have the same conventions about color use as we Europeans) - I'd suggest to switch it over to the conventional assignment. - After the first attempt to compile some code, I noticed that the coding line markers have gotten enormously blown up. That makes for a "slight" problem when using breakpoints: the breakpoint markers, which didn't receive the same pressure obviously, can hardly be recognized any more. If the blown up markers should stay, I propose to apply the same pressure to all of them, and make sure breakpoints are shown _above_ all other markers, because they're the ones you _need_ to see when they're used. -- -- (Weitergabe von Adressdaten, Telefonnummern u.ä. ohne Zustimmung nicht gestattet, ebenso Zusendung von Werbung oder ähnlichem) ----------------------------------------------------------- Mit freundlichen Grüßen, S. Schicktanz ----------------------------------------------------------- _______________________________________________ mseide-msegui-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
