This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
See screenshot. dev-030325. Obviously it should only include a given template in the recently-used list at most once (in the position corresponding to the most recent use).
Created attachment 9590 [details] Screenshot of problem
It works for me, NewTemplateAction.isRecent() return if a template is list ot not. If it contained in recent list that is not added more. It works also with "API Test Script" template. What build were you used when you saw it? This code has been changed 2 weeks ago. Another issue is that recent list is not reordered to the positions corresponding to the most recent use. I'm going to file a issue about it.
030325, as I say. Now I cannot reproduce it. Maybe just a result of some temporary bad code that is now cleaned up?
Jesse, I have never seen it , too.
I close as worksforme for now, if it reappears again, pls. reopen. Thanks.
Happened to me again using NB 3.5 Beta (official download) with a fresh user dir. Had installed apisupport NBMs, made a new Module JAR from template, restarted, done it again. See screenshot. Still not sure exactly how to reproduce.
Created attachment 10047 [details] New screenshot - 3.5 Beta
Happened to us again in 3.5 release with JSP template. Still not sure what the trigger condition is.
Happened in Nevada final release as well. We need to fix it because new ME release is based on nevada.
I think I see it now. Start NB 3.5 w/ a fresh user dir. Expand sampledir. File -> New, Other -> HTML File, select sampledir and name "foo". Repeat with name "bar". Now right-click sampledir -> New and you see "HTML File" listed twice. NewTemplateAction.isRecent should probably use getRecentList(), not use the raw variable recentList which may be out of date already. It is is not cleared or recreated by addRecent for some reason - though it certainly could be, without even needing to call getRecentFolder().getChildren(). Using the context menu after adding a recent item does recreate the list and prevent duplicated from being added, it seems, but the Ctrl-N or File -> New style does not touch the cached list.
fixed in maintrunk. The recent list is read at first time and a flag recentChanged is correctlly updated.
verified in NB3.6 RC1