From: SourceForge.net <no...@so...> - 2003-03-28 16:56:10
|
Bugs item #711270, was opened at 2003-03-28 10:53 You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100588&aid=711270&group_id=588 Category: plugins Group: None Status: Open Resolution: None Priority: 5 Submitted By: Chris Kent (cjkent) >Assigned to: James Wilson (jiwils) Summary: clicking tree in AntFarm 1.3 not selecting build file Initial Comment: AntFarm 1.3 does not set the current build file until the "Run Current Target" button is clicked. until this is done for the first time double-clicking a build file node in the tree expands the tree and shows and error "No build file selected". right clicking a build file and selecting "Execute default target: <whatever>" gives the same error. clicking a build file in the tree doesn't make that the current build file (which it did in 1.2). jEdit 4.1 final, AntFarm 1.3, jdk 1.4.1_02, win2k ---------------------------------------------------------------------- >Comment By: James Wilson (jiwils) Date: 2003-03-28 17:09 Message: Logged In: YES user_id=688607 Indeed. I fixed the Console popup problem and modified the Run button to load the build file instead of just selection. However, I missed the ability of the double-click to run a target. For now, use the Run button, but I'll post AntFarm 1.3.1 with a patch for this to the community web site this weekend. ---------------------------------------------------------------------- Comment By: Chris Kent (cjkent) Date: 2003-03-28 11:29 Message: Logged In: YES user_id=353578 I've made a quick change and reinstated the behaviour from version 1.2 that I was missing (selecting the project on clicking in the tree) but it also reinstates the irritating bug where the console pops up the first time a build file is selected (I have AntFarm and the console docked in the same place). this only occurs if the console hasn't been shown before. if I open the console before AntFarm then the problem goes away. I'm assuming that DockableWindowManager.addDockableWindow() always shows the new window, and that's what's causing the problem in this case. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=100588&aid=711270&group_id=588 |