MPLAB X IDE 3.60/3.61/3.65/4.00/4.01不会记录寄存器名称

您可以尝试清除MPLAB缓存文件。由于它没有正常工作，请拒绝从以前的安装导入设置。



      以下为原文

    You can try clearing the MPLab cache files.
And since it did not work properly, say no to import settings from previous installation.

我刚刚清除了MPLAB 3.60缓存目录和设置目录。然后启动MPLAB 3.60，没有从先前的版本导入任何东西：没有改变，问题仍然是完全相同的。



      以下为原文

    I've just cleared the MPLab 3.60 cache directory and the settings directory. Then started MPLab 3.60 without importing anything from the previous version: nothing changed, the problem is still exactly the same.
 

我可以在3.60 /Wooz 7（所有适用的更新应用）/PIC16LF18855上重复这个问题。这里我所观察到的是：寄存器的着色失败（例如状态）发生在最左边的文件IF上，因为它在MPLABX的最后一个会话中打开。如果我关闭文件并重新打开它，那么着色是意料之中的。如果我可以插入图像，我会在下面。为了记录，我清理了高速缓存，当我移动到3.60其他原因。GelnPeDIT 1：尝试附加图像。



      以下为原文

   


I can repeat this issue on 3.60 / Windoz 7 (all applicable updates applied) / PIC16LF18855.
 
Here's what I've observed:
 
The coloring failure for registers (for example STATUS) occurs on the left-most file IFF it was opened because it was open in the last session of MPLabX.  If I close the file and re-open it, the coloring is as expected.  If I can insert images, I will below.
 
For the record, I cleared the caches when I moved to 3.60 for other reasons.
 
GlennP
 
Edit 1: Trying to attach images again.
   Attached Image(s)

在我的例子中，问题并不总是在最左边的文件上。有时是第一个，有时是第二个…



      以下为原文

    In my case the problem isn't always on the leftmost file. Sometimes the first, sometimes the second...

这太糟糕了，MCHP很难找到。我的测试不是详尽无遗的，所以我相信你的结果。但我只看到了我所描述的。-（你在一个给定的会话中打开的文件中看到它，还是在我观察到的从最后一个会话中传递的文件中看到它？GP



      以下为原文

   


That's too bad - it will be harder for MCHP to find.
 
My testing was not exhaustive, so I believe your results.  But I've only seen what I described.  :-(
 
Do you see it in files you open in a given session or is it in files "carried over from the last session" as I observed?
 
GP

我只是尝试新鲜地打开各种新的文件，和他们的问题没有出现。现在问题只在于前一届会议上的文件。但昨天的问题有时也出现在文件刚刚打开。就在今天，我清除了MPLAX X缓存，也许它解决了这个问题的部分。版本3.55没有重新打开在最后一个会话中打开的文件：这个问题可能与同一个bug有关吗？



      以下为原文

    I just tried to freshly open various new files, and an them the problem doesn't appear. Now the problem is only on the files carried over the previous session. But yesterday the problem sometimes also appeared on the files just opened. As today I cleared the MPLAB X cache, maybe it solved this portion of the problem.
The version 3.55 did not re-open the files opened in the last session: may be this problem is related to the same bug?
 

目前我只看到带有源/包含文件的问题。我会重新发布，如果我注意到新打开的文件，但不到目前为止。我开始了3.60清除清除。我看到的是，3.55将移交文件，如果你选择“显示开始页”。你可以关闭开始页面，但是如果你没有选择下一次自动出现它，“携带的”文件会很短暂地出现，但随后消失。



      以下为原文

   
 
I currently see the problem only with carried over source/include files.  I'll repost if I notice newly opened files but not so far.  I did start out 3.60 with cleared cache.
 

 
What I saw was that 3.55 would carry over files IFF you selected "Show Start Page".  You could close the Start Page, but if you didn't select having it appear automatically the next time, the "carried over" files would appear very briefly but then go away.
 
GP

我使用V3.55仅仅几个小时，因为它有一个严重的问题与它的颠覆（SvN）集成，所以我放弃并继续使用V3.51。然后我用V3.60交换，当它被释放两天前。到目前为止，我发现的唯一错误是语法高亮显示。



      以下为原文

    I used v3.55 only for a few hours, because it had a serious problem with its subversion (SVN) integration, so I gave up and continued using v3.51. Then I switched using v3.60 when it was released two days ago. The only bug I found so far is the syntax highlighting.

我还返回到V3.51.内存占用，MPLAX内存在Windows O/S分配后没有释放，Bug重新介绍。



      以下为原文

    I also went back to v3.51.
 
Eating up memory, mplab x memory not freed after allocation from windows o/s, bug re-intruduced.

V3.55是辆马车。V3.60似乎更好。



      以下为原文

    v3.55 was buggy. v3.60 seems to be better.

每一个版本都有bug。它永远不会是100%。你仍然不能把文件添加到项目中，这是一个硬币的扔，如果他们留在下一个会议。



      以下为原文

    Every version has bugs.
It will never be 100%.
 
You still can not add files to projects, it's a toss of a coin if they remain there on next session.
 

我注意到另外一件事：当寄存器名称的语法高亮不起作用时，MPLAB X V3.60错误地突出显示了其他术语。我不能附加图像（我得到许可拒绝EROR），所以我试着在这里显示代码。我注意到在图像中显示的问题（PIC18F46J50，.ASM文件）：好的BZ等待调用WaFFETCH返回；坏BZ FAWE调用WAITFEATE返回；编辑器识别等待为关键字，而不是关键字。因此，编辑器似乎使用了一些错误的关键字表，在这个案例中。也有保存关键字的问题。



      以下为原文

    I noticed one more thing: when the syntax highlight of the registers names doesn't work, MPLAB X v3.60 incorrectly highlight some other term. I'm not able to attach the images (I get a permission denied erorr), so I try to show the code here. I noticed the problem in the line shown in the images (PIC18F46J50, .asm file):
Good
 
        bz      fwait
        call    wait
fwait   return                  ;

 
 
Bad
        bz      fwait
        call    wait
fwait   return                  ;
 
 
The editor recognizes wait as a keyword, while it's not a keyword.
So it seems that the editor uses some wrong keyword table, in this case.
 
PS: same problem with the save keyword, too.
 

你的图像没有显示。我没有得到等待关键字错误，我得到保存。



      以下为原文

    Your images are not displayed.
 
I don't get the wait keyword bug, I get save instead.

@ GTT2015：我更正了我的帖子。我检查了：我和保存关键字也有同样的问题。



      以下为原文

    @Gort2015: I corrected my post.
 
I checked: I have the same problem with the save keyword, too.

我讨厌ASM的是，如果我点击MPU寄存器，即OSCCon，那么每个寄存器的出现都会被高亮显示。希望我关闭它。安装V3.60后，bug已经消失了，但我希望他们会列出所有修复和增强中的修复错误。如果我在编辑器中克隆了一个ASM窗口，则un/注释图标在克隆窗口中不起作用。需要检查它是否被修复。将现有项添加到项目源FILE。需要检查它是否是固定的一个真正的主要错误我反复遇到，我编辑一些文件，编译，一切似乎很好，我烧到PIC，发现文件没有改变。看起来不错，但在重新启动之后，我发现文件中没有任何变化。他们应该在MS VisualStudio上工作。



      以下为原文

    What I hate about asm is that if I click on a mpu register, i.e. OSCCON then every occurence of that register becomes highlighted.  Wish I turn that off.
 
After installing v3.60 that bug has gone but I wish they would list all the fixed bugs in Repairs and Enhancements.
 
If I clone an asm window in the editor, the un/comment icon does not work in the cloned window.
Need to check if that is fixed.
 
Add Existing Item to project source files.
Need to check if that is fixed
 
One really major bug I come across now and again, I edit some file, compile and all seems well, I burn to pic and discover the file has not changed.  It looks ok but after a restart I find nothing has changed in that file.
 
They should get this working on MS Visual Studio.

阿门。VS（2012 -我最后一个）开始Soooooo快得多。很少有崩溃，有反应。不确定Mo是否足够接近端口到Linux会很容易。我甚至想过要自己做这件事，但是调试器吓了我一跳。在我有一大堆空闲时间的时候，剩下的东西可能是可以管理的。[笑话] GP



      以下为原文

   


Amen to that.  VS (2012 - last one I have) starts sooooooo much faster.  Very few crashes, responsive.
 
Not sure if Mono is similar enough that a port to Linux would be easy though.
 
I've even thought about doing this myself, but the debugger scares me.  The rest might be manageable in the distant future when I have a bunch of free time.  [<-- Joke]
 
GP

很多工作都会涉及到，你需要一支团队箭或其他东西。



      以下为原文

    A lot of work would be involved.
You'd need a Team Arrow or something.