1.2.3 beta: Renaming custom frame variable

[cebarne2]

1) A tabfolder, tabitem, and scrolledComposite inside tabitem
2) Used a custom frame in the composite (SWT Frame wizard)
3) Renamed the frame variable from buildPaths to pgBuildPaths
-my Frame class is buildPaths and SWT Designer used that same name as the variable name
-I renamed it to avoid potential conflicts



After step #2:

Code: Select all

final buildPaths buildPaths = new buildPaths(scrolledComposite, SWT.NONE);
                  buildPaths.setSize(735, 303);
                  scrolledComposite.setContent(buildPaths);

After renaming in step #3:

Code: Select all

final pgBuildPaths pgBuildPaths = new pgBuildPaths(scrolledComposite, SWT.NONE);
                  pgBuildPaths.setSize(735, 303);
                  scrolledComposite.setContent(pgBuildPaths);

It seems that using a custom frame, it inherits the Frame's class as the variable name. Not good. Then, when I rename the variable via the control properties, it renames both the Class and instance names. This introduces an error in the code.

Regardless, I like this custom frame functionality.

Thanks

[Eric Clayberg]

1) A tabfolder, tabitem, and scrolledComposite inside tabitem
2) Used a custom frame in the composite (SWT Frame wizard)
3) Renamed the frame variable from buildPaths to pgBuildPaths
-my Frame class is buildPaths and SWT Designer used that same name as the variable name

Are you saying that your class name is "buildPaths" rather than "BuildPaths"? Shouldn't that class name be capitalized? The default variable name for a class is the class name with the first letter made lowercase. In this case, they would end up being the same thing. We will add some code to test for that case in the next update.

[cebarne2]

Yeah, looks like I screwed up a bit on the naming convention. But, it is only a convention.

Adding a check for this condition would only make the plug-in that much more robust.

Thank you for your consideration with this issue.

[Eric Clayberg]

Adding a check for this condition would only make the plug-in that much more robust.

A new v1.2.3 beta has been released that adds a check for this condition.