Services & Resources / Wolfram Forums
-----
 /
MathGroup Archive
2007
*January
*February
*March
*April
*May
*June
*July
*August
*September
*October
*Archive Index
*Ask about this page
*Print this page
*Give us feedback
*Sign up for the Wolfram Insider

MathGroup Archive 2007

[Date Index] [Thread Index] [Author Index]

Search the Archive

Re: Re: Compatibility woes

  • To: mathgroup at smc.vnet.net
  • Subject: [mg76194] Re: [mg76099] Re: Compatibility woes
  • From: DrMajorBob <drmajorbob at bigfoot.com>
  • Date: Thu, 17 May 2007 06:11:05 -0400 (EDT)
  • References: <f295kp$n4k$1@smc.vnet.net> <30568553.1179316638063.JavaMail.root@m35> <op.tsfni5p3qu6oor@monster.ma.dl.cox.net> <13780686.1179343455242.JavaMail.root@m35>
  • Reply-to: drmajorbob at bigfoot.com

> slider moves directly to the mouse position. Concerning the slider  =

> speed, we found that it is reasonably responsive (not too fast or not =
 =

> too slow) for many. Actually, it is up to the system mouse sensitivity=
  =

> setting, not Mathematica.

I belatedly realize that can't be true.

No matter how sensitive (or not) the mouse may be, the maximum mouse  =

movement (equal to the visible height of the control) must equate to  =

moving through ALL members in the list. So the speed at which the list  =

flies by, for ANY given mouse movement, is (and has to be, for a slider)=
  =

proportional to the number of entries in the list.

Hence sliders are tolerable for small lists, intolerable for very long  =

lists. For a list with millions of entries, one pixel of mouse movement =
on  =

the screen could equate to thousands of entries, but maybe we're only  =

seeing five or ten.

Screen resolution has an effect; high resolution => short visible cont=
rol  =

=> faster movement through the list. I run my screen at 1280x1024, so =
the  =

"speed" I'm looking at is 25% greater than what you'd see at 1024x768.

No?

Bobby

On Wed, 16 May 2007 14:22:08 -0500, Yu-Sung Chang <yusung at wolfram.com>  =

wrote:

> DrMajorBob wrote:
>> ColorData["Legacy", "Images"] returns an error:
> My mistake. Should be "Image". Also, an interactive tool can be called=
  =

> by "Panel".
>>
>> ColorData::notprop: Images is not a known property for ColorData. Use=
 \
>> ColorData["Properties"] for a list of properties.
>>
>> And neither ColorData["Legacy"][LightGreen] nor  =

>> ColorData["Legacy"][PaleGreen] returns a color (RGB code).
> The name should be given as a string (otherwise, there would be no poi=
nt  =

> of having this special paclet, since they were already symbols).  =

> ColorData[] does not define new symbols.
>>
>> How do I Plot on a PaleGoldenrod background?
>>
>> Plot[Sin[x], {x, -Pi, Pi}, Background -> PaleGoldenrod]
> Background->ColorData["Legacy", "PaleGoldenrod"]
> Please remember that there are a lot of overlaps in names between colo=
r  =

> sets. For instance, our "Legacy" color set (derived from  =

> Graphics`Colors`) and "HTML" named color set share a huge number of  =

> names (and the defined colors are different).
>>
>>> Please refer ColorData documentation for further information. Also,
>>> there is an interactive palette under "Palettes" menu, called
>>> "ColorSchemes", which will display all the available colors.
>>
>> When I select "Named" and "Legacy", I get a scroll bar that's unusabl=
e.  =

>> I can't arrow down through the list or use the page-down key, making =
 =

>> sure that I see them all. I can't click on the slider without moving =
 =

>> too far and missing some. I can't find Blue except by trial and error=
  =

>> (even after sorting by name).
> If you noticed, a palette does not steal the keyboard focus from your =
 =

> working notebook. For various reasons, but mainly because some  =

> functionalities (for instance, "Insert") want to know the focused  =

> notebook. The workaround is making shortcuts from some unassigned keys=
,  =

> but it is definitely not a pretty solution.
>>
>> When I try "paging down" in the list by clicking the control, I get  =

>> different results on every attempt. Sometimes the first color after  =

>> Azure is BlanchedAlmond. Sometimes it's BrownMadder. Et cetera.
> You are clicking a slider bar. Unlike the system slider, Mathematica  =

> slider moves directly to the mouse position. Concerning the slider  =

> speed, we found that it is reasonably responsive (not too fast or not =
 =

> too slow) for many. Actually, it is up to the system mouse sensitivity=
  =

> setting, not Mathematica.
>
> If you find that the palette is hard to use, please try  =

> ColorData["Legacy","Panel"].
>>
>> Nobody at Wolfram ever tried to USE this palette, it seems to me.
> I understand that the scrollbar can be awkward, especially if you are =
 =

> using a touchpad. It is quite possible in the future that we add arrow=
  =

> buttons at the top and bottom for single step moves.
>
> Also, the documentation deals with the function in great detail. Many =
of  =

> your questions are already answered in there (first few "basic"  =

> examples).
>
> Sincerely,
>
> Yu-Sung Chang
> Kernel Technology
> Wolfram Research, Inc.
>



-- =

DrMajorBob at bigfoot.com


  • Prev by Date: Re: Where is the Mathematica Book in Documentation Center?
  • Next by Date: Re: TeXForm and custom LaTeX macros
  • Previous by thread: Re: Re: Compatibility woes
  • Next by thread: Re: Re: Compatibility woes