|
From: Nik Trevallyn-J. <ni...@us...> - 2010-08-04 02:30:51
|
On 08/03/2010 10:51 PM, Shlomy Reinstein wrote: > Hi, > > First, someone should check why the new field (int xyz) vanishes in (2). I assumed that there was a setting for that somewhere which I hadn't yet found (I'm still getting used to where all the various options settings are...) ... Ok, found it. Beside the "fields" checkbox in JavaSidekick, is "include primitives". Checked that, and "int xyz" now just moves from the method list to the field list. > Second, you may want to disable (unload) DirtyGutter - perhaps it > paints over the error icon... Can you try and let me know? I had assumed that it was not a problem because PMD had managed to paint warnings all over the gutter. :o) But I've tried now, and still no errors or warnings are displayed. The behaviour with SideKick is that it seems to assume the most likely match from the grammar - even if the code is incomplete. For example, if I type "protected ArrayList(String> xyz", SideKick displays it as a contructor - having apparently parsed it as a (possible) method with no return type. So, with my installation and settings, it seems SideKick is determined to see the glass half full rather than the glass half empty :o) (possible good code rather than possible errors). Cheers! Nik |