谢谢你让我们注意到这一点。
根据您使用的输入字段的类型,在使用大写与小写'm'时,行为看起来确实存在差异。
当设置刺激频率时,'m'和'M'都被解释为“MHz”,但在制造商位置输入编辑框中,'m'被解释为milli。
虽然这种不一致令人困惑,但背后有一个原因。
频率激励值永远不会在毫赫兹范围内,但如果时域打开或者通道设置为CW时间扫描,则标记位置可以是毫秒范围,如果通道处于通电状态,则标记位置可以是毫秒范围
扫描模式。
因此,在标记条目编辑框中,“m”和“M”单位加速键的解释方式不同。
但是,可以检测标记条目的上下文并确定标记是否在具有x轴正常频率范围的迹线上,并忽略用户按下键盘上的“m”键时的情况。
标准扫描条件(请注意,前面板上的M和m单元位于两个不同的物理键上)。
我会将您的反馈意见传递给UI设计团队,看看我们是否可以在即将发布的版本中增强此行为。
以上来自于谷歌翻译
以下为原文
thank you for bringing this to our attention. it does look like there is a difference in behavior when it comes to using upper versus lower case 'm' depending on the type of entry field you are using. when setting a stimulus frequency, both 'm' and 'M' are interpreted as "MHz", but in a maker position entry edit box, 'm' is interpreted as milli. while this inconsistency is confusing, there is a reason behind it. Frequency stimulus values can never be in milli-Hz range, but a marker position can be in milli-second range if time domain is turned on or the channel is set to CW Time sweep or in milli-dB range if the channel is in power sweep mode. for this reason, in marker entry edit boxes, 'm' and 'M' unit accelerator keys are interpreted differently. However, it is possible to detect the context of the marker entry and determine if the marker is on a trace that has a normal frequency range for x-axis and ignore the case when the user presses the 'm' key on the keyboard under the standard sweep conditions (notice that on the front panel the M and m units are on two different physical keys). I will pass your feedback on to the UI design team and see if we can enhance this behavior in one of our upcoming releases.
谢谢你让我们注意到这一点。
根据您使用的输入字段的类型,在使用大写与小写'm'时,行为看起来确实存在差异。
当设置刺激频率时,'m'和'M'都被解释为“MHz”,但在制造商位置输入编辑框中,'m'被解释为milli。
虽然这种不一致令人困惑,但背后有一个原因。
频率激励值永远不会在毫赫兹范围内,但如果时域打开或者通道设置为CW时间扫描,则标记位置可以是毫秒范围,如果通道处于通电状态,则标记位置可以是毫秒范围
扫描模式。
因此,在标记条目编辑框中,“m”和“M”单位加速键的解释方式不同。
但是,可以检测标记条目的上下文并确定标记是否在具有x轴正常频率范围的迹线上,并忽略用户按下键盘上的“m”键时的情况。
标准扫描条件(请注意,前面板上的M和m单元位于两个不同的物理键上)。
我会将您的反馈意见传递给UI设计团队,看看我们是否可以在即将发布的版本中增强此行为。
以上来自于谷歌翻译
以下为原文
thank you for bringing this to our attention. it does look like there is a difference in behavior when it comes to using upper versus lower case 'm' depending on the type of entry field you are using. when setting a stimulus frequency, both 'm' and 'M' are interpreted as "MHz", but in a maker position entry edit box, 'm' is interpreted as milli. while this inconsistency is confusing, there is a reason behind it. Frequency stimulus values can never be in milli-Hz range, but a marker position can be in milli-second range if time domain is turned on or the channel is set to CW Time sweep or in milli-dB range if the channel is in power sweep mode. for this reason, in marker entry edit boxes, 'm' and 'M' unit accelerator keys are interpreted differently. However, it is possible to detect the context of the marker entry and determine if the marker is on a trace that has a normal frequency range for x-axis and ignore the case when the user presses the 'm' key on the keyboard under the standard sweep conditions (notice that on the front panel the M and m units are on two different physical keys). I will pass your feedback on to the UI design team and see if we can enhance this behavior in one of our upcoming releases.
举报