WinGui:

- Fix Adaptive Quantization Strength ToolTip

git-svn-id: svn://svn.handbrake.fr/HandBrake/trunk@3427 b64f7644-9d1e-0410-96f1-a4d463321fa5

2 files changed, 3 insertions, 5 deletions

diff --git a/win/C#/Controls/x264Panel.Designer.cs b/win/C#/Controls/x264Panel.Designer.cs
index b9849e71f..e445c179b 100644
--- a/win/C#/Controls/x264Panel.Designer.cs
+++ b/win/C#/Controls/x264Panel.Designer.cs
@@ -615,7 +615,9 @@ namespace Handbrake.Controls
             this.slider_adaptiveQuantStrength.Name = "slider_adaptiveQuantStrength";

             this.slider_adaptiveQuantStrength.Size = new System.Drawing.Size(131, 45);

             this.slider_adaptiveQuantStrength.TabIndex = 88;

-            this.ToolTip.SetToolTip(this.slider_adaptiveQuantStrength, resources.GetString("slider_adaptiveQuantStrength.ToolTip"));

+            this.ToolTip.SetToolTip(this.slider_adaptiveQuantStrength, "Adaptive quantization controls how the encoder distributes bits across the frame." +

+                    "  \r\nHigher values take more bits away from edges and complex areas to improve ar" +

+                    "eas with finer detail");

             this.slider_adaptiveQuantStrength.Value = 10;

             this.slider_adaptiveQuantStrength.Scroll += new System.EventHandler(this.widgetControlChanged);

             // 

diff --git a/win/C#/Controls/x264Panel.resx b/win/C#/Controls/x264Panel.resx
index 26a9e886c..488377436 100644
--- a/win/C#/Controls/x264Panel.resx
+++ b/win/C#/Controls/x264Panel.resx
@@ -232,10 +232,6 @@ Baseline profile, as required for iPods and similar devices, requires weighted P
 Note that some devices and players, even those that support Main Profile, 

 may have problems with Weighted P-frame prediction: the Apple TV is completely incompatible with it, for example.</value>

   </data>

-  <data name="slider_adaptiveQuantStrength.ToolTip" xml:space="preserve">

-    <value>Psychovisual Rate Distortion Optimization sure is a mouthful, isn't it? Basically, it means x264 tries to retain detail, for better quality to the human eye, 

-as opposed to trying to maximize quality the way a computer understands it, through signal-to-noise ratios that have trouble telling apart fine detail and noise.</value>

-  </data>

   <data name="combo_pyrmidalBFrames.ToolTip" xml:space="preserve">

     <value>This is the distance x264 searches from its best guess at the motion of a block in order to try to find its actual motion.  

 Doesn't apply to Diamond or Hexagon search options.