完善资料让更多小伙伴认识你,还能领取20积分哦, 立即完善>
您好,我正在使用A.09.80.15固件,我正在尝试为我在Megahertz单元中配置的SMC通道设置标记。
如果我尝试输入值(即200 MHz)并使用小写的“m”,则不会设置它。 只有当我使用大写的“M”时才会将其设置为标记的正确频率值。 我尝试了Gigahertz单位(即1GHz)的相同实验,无论是否使用小写或大写'G',它都能正常工作。 起初,我认为这是一个标记设置问题,直到我尝试了大写的'M'。 只是想报告错误,以防其他人遇到同样的问题。 最好的问候,rok 以上来自于谷歌翻译 以下为原文 Hello, I am using A.09.80.15 firmware and am trying to set a marker for an SMC channel I am configuring in the Megahertz units. If I try to type in the value (i.e. 200 MHz) and use a lowercase 'm', it will not set it. Only if I use an uppercase 'M' does it set it to the right frequency value for the marker. I tried the same experiment for the Gigahertz units (i.e. 1GHz) and it worked regardless of whether a lowercase or uppercase 'G' was used or not. At first, I thought it was a marker setting issue until I tried out the uppercase 'M'. Just wanted to report the bug in case someone else encountered that same problem. Best regards, rok 附件 |
|
相关推荐
4个回答
|
|
谢谢你让我们注意到这一点。
根据您使用的输入字段的类型,在使用大写与小写'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. |
|
|
|
Topcbpcba 发表于 2019-4-15 08:34 你好,谢谢你的回复。 我对GUI的行为感到困惑,因为我一直输入'200'然后是小'm',标记显示会瞬间闪烁并仍然显示190 MHz,让我相信它已更新但不接受该频率 价值,这对我没有意义。 当我尝试千兆赫单位示例时,我才怀疑它可能是一个区分大小写的问题。 我只想提醒其他人注意,以防他们遇到同样的困难。 谢谢,rok 以上来自于谷歌翻译 以下为原文 Hi, Thanks for the reply. I was confused by the GUI behavior, because I kept entering '200' followed by the little 'm' and the marker display would flash momentarily and still show 190 MHz, leading me to believe that it had updated but wouldn't accept that frequency value, which didn't make sense to me. Only later did I suspect it might be a case-sensitive issue when I tried the gigahertz unit example. I just wanted to alert other folks to be aware in case they encountered the same difficulty I did. Thanks, rok |
|
|
|
蓝色冰汐 发表于 2019-4-15 08:43 使用键盘输入值时会出现相同(恼人)问题。 大M或小m解释不一致,但取决于背景。 但依赖性并不像我想的那样强大(标记就是一个例子)。 以上来自于谷歌翻译 以下为原文 The same (annoying) issue occurs when using a keyboard to enter the values. The big M or little m interpretation is not consistent, but depends upon context. But the dependency is not as robust as I would like (marker being one example). |
|
|
|
> {quote:title = Dr_joel写道:} {quote}>使用键盘输入值时会出现同样(烦人)的问题。 使用键盘是唯一的用例,这是一个问题。 在前面板上,小'm'和大'M'单元乘法器是两个不同的物理键,但在标准键盘上它们不是,因此Rok描述的问题。 我们的PNA UI用户已将此问题添加到他们的UI增强候选列表中。 以上来自于谷歌翻译 以下为原文 > {quote:title=Dr_joel wrote:}{quote} > The same (annoying) issue occurs when using a keyboard to enter the values. using the keyboard is the only usecase where this is an issue. On the front panel the little 'm' and big 'M' unit multiplyers are two different physical keys, but on a standard keyboard they are not, hence the problem described by Rok. Our PNA UI brethren have already added this issue to their list of UI enhancement candidates. |
|
|
|
只有小组成员才能发言,加入小组>>
1215 浏览 0 评论
2345 浏览 1 评论
2149 浏览 1 评论
2018 浏览 5 评论
2898 浏览 3 评论
952浏览 1评论
关于Keysight x1149 Boundary Scan Analyzer
691浏览 0评论
N5230C用“CALC:MARK:BWID?”获取Bwid,Cent,Q,Loss失败,请问大佬们怎么解决呀
793浏览 0评论
1215浏览 0评论
小黑屋| 手机版| Archiver| 电子发烧友 ( 湘ICP备2023018690号 )
GMT+8, 2024-11-19 05:24 , Processed in 1.450958 second(s), Total 82, Slave 65 queries .
Powered by 电子发烧友网
© 2015 bbs.elecfans.com
关注我们的微信
下载发烧友APP
电子发烧友观察
版权所有 © 湖南华秋数字科技有限公司
电子发烧友 (电路图) 湘公网安备 43011202000918 号 电信与信息服务业务经营许可证:合字B2-20210191 工商网监 湘ICP备2023018690号