• Replies 2 replies
  • Subscribers 18 subscribers
  • Views 612 views
  • Users 0 members are here
Options
Related

Eclipse plugin: Build For Device Wizard's "Finish" button disabled by default

WillNorthYork
In the Connect IQ SDK 3.0.4 Eclipse plugin, the Build For Device Wizard's "Finish" button is greyed out by default, even when all of the valid choices from the last build are displayed. You have to change one of the fields (such as Device), even if you're "changing" the value to what it already is. This is a small issue but a little annoying if you rebuild a lot.

Tried an older SDK/plugin (2.4.2) (previously installed on a different computer) and it has the same problem, so it doesn't seem to be a regression.
  • When I see this, it's often that the output directory isn't available when you open the dialog. So when I connect a device, I'll wait for windows to see it before I open the dialog. For MTP devices, I'll build to c:\garmin\apps and then copy it to the device, as MTP devices don't show in the wizard.
  • Thanks jim_m_58 but that's clearly not the case with my bug report.

    even when all of the valid choices from the last build are displayed


    I have seen what the dialog looks like when the output directory isn't available. It says "Please specify a valid output directory". But even when that's the case, I don't see that error message until I touch any field on the dialog.

    In this case, my output directory is on my system drive. Furthermore, if the problem was the output directory, then it wouldn't be solved by simply touching any field -- even "changing" a dropdown to the exact same value without toggling it. To me it looks like a classic case of form validation logic only being applied when a field is changed, and not at init time. But who knows? I just know that it's never worked for me, as long as I can remember.

    I actually started looking at CIQ last year -- which is why I have an old SDK on a different computer -- so it's not the first time I noticed this bug. I was just sort of surprised it still exists.

    If it makes a difference, I'm on Windows 10, Eclipse 4.9.0. I've seen the same bug with the old SDK/plugin (2.4.2) and an older version of Eclipse.

    Maybe it's just me, since you're not seeing this problem, but I'm seeing it on two different computers, with two different versions of the SDK plugin.