按钮怎么稳定

所以我认为这一切的真正原因是触摸驱动器不能正常工作。据说，双缓冲似乎与按钮按下时的显示方式一团糟。我相信，在低成本无控制器的框架下，我已经为每一个缓冲设置了正确的：帧Buffer Mode（双缓冲区），V-同步刷新策略（常规）等。当我只在1和2之间切换缓冲区计数时，问题就开始了。我现在正在使用。如果我将缓冲区计数设置为1，那么按钮会像我所期望的那样运行：只要按下按钮，按钮就处于按下状态。如果我反复点击一个按钮，我也能看到。现在，如果我把缓冲区计数设置为2，那么按钮点击只是眨眼。我可以按下和按住按钮，但我只会得到一个，快，眨眼。有时，我可以得到按钮，使陷入紧张状态。现在，代码可能会认为它处于未被压缩的状态，因为我没有检查过，但是有些东西肯定是错误的。有什么想法吗？我使用图像按钮，所以按下状态图像仅仅是未压缩状态的负像。我能想到的最好的是，在比较快的情况下，触摸驱动器和双缓冲的复制之间存在某种竞争状态。



      以下为原文

    So I think that the real cause of all of this was the touch driver not working properly. That having been said, double buffering seems to mess with how the buttons are displayed when pressed. I believe that I have everything set up correctly for double buffering as per the options under Low Cost Controllerless: Frame Buffer Mode (Double Buffer), V-Sync Refresh Strategy (Conventional), etc. The problem comes into play when I toggle the buffer count between 1 and 2 for the only layer that I'm currently using.
 
If I set the buffer count to 1, then the buttons will behave as I would expect: as long as I'm pressing down the button is in the pressed state. If I click on a button repeatedly I can see that too.
 
Now, if I set the buffer count to 2 then the button clicks are just blinks. I can press and hold the button down but I'll only get that one, quick, blink. Some times I can get the button to get caught in the pressed state. Now the code may actually think it's in the unpressed state as I haven't check that, but something is definitely wrong.
 
Any thoughts? I'm using image buttons, so the pressed state image is simply the negative image of the unpressed state. The best I can come up with is that there is some sort of race condition between the very fast, by comparison, touch driver and the copying that takes place with double buffering.

您好，首先，我听到您的关注，并将这一点传递给了团队。我们的电阻式触摸专家现在不在办公室，所以在几分钟之前，更多的响应即将到来。现在，你能告诉我们你正在使用什么平台（MCU和板）吗？我假设你现在知道有2个不同的触摸驱动程序，一个叫做10BITADC和另一个AdCouch。我们将走向一个统一的驱动程序与ADCTouch在未来。原来的10位ADC触摸是针对PIC32 MX。随着PIC32 MZ设备硬件的改变，这需要更新。我们和ADCTouch一起做了。现在在ARIAYQuiSupp应用程序中有一个硬件配置。然而，在V2.03B中，事情并不完美。在使PIC32 MZ工作时，需要进行一些硬件修改来显示这一点。这是因为我们没有本地电路板将电阻触摸面板连接到PIC32 MZ启动器套件上。此配置所需的修改在帮助手册中显示。对于和声V2.03B，我也理解驱动程序的改变并不完全支持PIC32 MX。它可能是来自和谐V2.02B的10BITADC驱动程序是更好的，因为我们没有更新新版本的最新版本。在我们的P2.22MX版本V2.02B版本中，这也有一个单独的应用程序配置用于校准。一旦我们了解了您的配置和驱动程序的起点，我们将尝试提供更多个性化的帮助。



      以下为原文

    Hello,
 
First, I hear your concern and have passed this along to the team.  Our resistive touch specialist is out of the office just now, so it will be a few days before more response is forthcoming.
 
For now, can you tell us what platform (MCU and board) you are working with?  I assume you are aware that there are 2 different touch drivers currently, one is called 10bitADC and the other ADCTouch.  We will be moving towards a unified driver with ADCTouch in the future.
 
The original 10-bit ADC touch was for PIC32 MX.  As the device hardware changed for PIC32 MZ, this required an update.  We did so with the ADCTouch.  There is now a hardware configuration for this in the aria_quickstart app.
 
Things are not perfect in Harmony v2.03b however.  In getting the PIC32MZ to work, it takes some hardware modifications to show this off.  That is because we did not have native boards to attach the resistive touch panel to a PIC32MZ starter kit.  The modifications needed for this configuration are shown in the help manual.
 
For Harmony v2.03b, I also understand that the change in drivers does not fully support PIC32 MX.  It could be that the 10bitADC driver from Harmony v2.02b is better, as we did not update the latest one for the new version.  In our Harmony v2.02b version for PIC32MX, this also has a separate application configuration for calibration.
 
We will try to supply more personalized assistance once we understand your configuration and what your driver starting point is.  

知道了。嗯，这可能是一个问题，因为我正在移动到PIC32 MZ2064 DAH176在自定义板，虽然我遵循Microchip的例子硬件和布局准则。那个董事会明天来，所以不用担心。



      以下为原文

    Got it. Well, it may be a moot point as I'm moving to the PIC32MZ2064DAH176 on a custom board, though I followed Microchip's example hardware and layout guidelines. That board comes in tomorrow, so no worries.