flash builder 4 - 按下 CTL+Space(用于定义 SkinClass)时出现 java.lang.NullPointerException 错误

发布于 2025-01-07 06:14:47 字数 1319 浏览 4 评论 0原文

由于某种原因,当我尝试为自定义组件定义 SkinClass 时,我开始遇到这个奇怪的问题。

错误消息:

出现问题:

“内容辅助”无法正常完成。请参阅日志以获取更多信息。

并且日志显示这两行

“Content Assist”没有正常完成。请参阅日志以获取更多信息。 java.lang.NullPointerException

我用谷歌搜索并发现其他一些人也收到此错误消息(使用 FB4 beta 版本)。 此处,很多人发布了各种解决问题的方法,似乎对他们有用,但没有一个技巧对我有用。

他们在这里发布的一些解决方案是

1) 退出 FB
2)删除此文件夹:.metadata\.plugins\com.adobe.flexbuilder.codemodel [在顶层

您的工作区文件夹] 3)重新启动FB

 此修复似乎只是暂时的。当我将一些新资产从资产 SWC 导入到我的项目中时,错误再次出现。


 最快的修复方法是关闭并重新打开 FB 项目。]

当我从 SWC 导入新资产或更新 SWC。为了避免完全重新启动 Eclipse 或 FB4,我 右键单击我正在处理的项目,转到属性,删除 包含我的 SWC 的文件夹并重新添加它们。这是一种痛苦,但是 这比退出并重新启动 IDE 更快。

在更新我的资产 SWC 后,我遇到了同样的错误,并且我已经 包含 SWC 的导入文件夹。如果我只导入 SWC,我就看不到这个 错误。我对此的解决方法是仅导入 SWC:s,而不导入文件夹,或者 更新 SWC 后(当您导入整个文件夹时)移动一些 “构建路径库”中的项目先向上然后向下列出。这 强制 Flash Builder 更新引用或其他内容。无论如何,那个 解决问题

似乎他们中的所有人(大多数?)在导入新资产时都遇到了这个问题(这不是我的情况)。我的情况不同,不确定是否与命中有关。昨天我安装了perforce(版本控制软件)并创建了perforce工作区来保存我的所有代码(包括flex)。我将整个 Flex 代码添加到 perforce 中,并开始在新的 perforce 工作区而不是原始工作区中工作。我最初只签出“src”文件夹,因为这是我要做的唯一更改,但我想它可能会给 FB 带来问题,因为它可能需要元数据文件夹的写入权限才能保存内部信息。

For some reason, I have started getting this weird issue when ever I try to define skinClass for my custom component.

Error message:

Problem Occured:

"Content Assist" could not complete normally. Please see the log for more information.

And the log shows these two lines

"Content Assist" did not complete normally. Please see the log for more information.
java.lang.NullPointerException

I have googled and found some others too were getting this error message (with FB4 beta version). Here, lot of people posted various methods how they resolved the issue and seems it worked for them but none of tricks has worked for me.

Some of solutions they have posted here are

1) Quit FB
2) Delete this folder: .metadata\.plugins\com.adobe.flexbuilder.codemodel [in the top level

of your workspace folder]
3) Restart FB

 this fix seems to be only temporary. Once I imported some new assets from an assets SWC into my project, the error re-appeared.


 The quickest fix is to close and re-open the FB Project.]

I too get this issue when I import new assets from a SWC or update a
SWC. To avoid having to restart Eclipse or FB4 altogether, I
right-click on the project I’m working on, go to properties, remove
the folder that contains my swcs and re-add them. It’s a pain, but
it’s faster doing that than quitting and restarting the IDE.

I get this same error after I have updated my assets SWC and I have
imported folder containing SWC. If I import just SWC, i don’t get this
error. My fix to this is either import only SWC:s, not folders, or
after updating SWC (when you have imported whole folder) move some
item in “Build Path Libraries” list first up and then down. This
forces Flash Builder to update references or something. Anyways, that
solves the problem

It seems like all (most?) of them got this issue when they were importing new assets (which is not in my case). My case is different, not sure if it has something to do wit hit. Yesterday I installed perforce (version controlling software) and created perforce workspace to keep all my code (including flex). I added entire flex code into perforce and started working in the new perforce workspace instead of the original workspace. I checked-out only the "src" folder initially because thats the only thing I am going to make changes, but I guess it might have created problem to FB because it might require write permissions on metadata folder to save the internal information.

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。
列表为空,暂无数据
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文