
| Key: |
FDT-2794
|
| Type: |
Bug
|
| Status: |
Closed
|
| Resolution: |
Fixed
|
| Priority: |
Critical
|
| Assignee: |
FDT Team
|
| Reporter: |
John Olson
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
File Attachments:
|
1.
FDT-2794.mov (4,24 MB)
|
|
Environment:
|
Mac OSX 10.7.4, FDT 5.5 MAX
|
|
| Review Type: |
Review by Product Owner
|
[Video added]
I renamed the folder that contains all my Flex SDKs and when I opened FDT to update the FDT settings, it put me back into the FDT setup screen. I tried repeatedly to use the FDT setup screen to fix the SDK location but it was near impossible to get it to search and find the updated SDKs. It was almost as if the path was cached. I tried to close the FDT setup screen but it would quit FDT as a result. In the end, I was able to work around it by moving the dialog to the side, and opening the FDT app preferences and fixing the SDK from there. This was a MAJOR pain in the butt. If my SDKs aren't set up properly, FDT should allow me to run the app and not try to force me to fix via the setup screen or worse, quit the app when I'm trying to fix it (not through the setup screen). I think the new setup screen is a nice convenience when someone is first starting up FDT, but it shouldnt try to force me to do anything other than pick which license.
|
|
Description
|
[Video added]
I renamed the folder that contains all my Flex SDKs and when I opened FDT to update the FDT settings, it put me back into the FDT setup screen. I tried repeatedly to use the FDT setup screen to fix the SDK location but it was near impossible to get it to search and find the updated SDKs. It was almost as if the path was cached. I tried to close the FDT setup screen but it would quit FDT as a result. In the end, I was able to work around it by moving the dialog to the side, and opening the FDT app preferences and fixing the SDK from there. This was a MAJOR pain in the butt. If my SDKs aren't set up properly, FDT should allow me to run the app and not try to force me to fix via the setup screen or worse, quit the app when I'm trying to fix it (not through the setup screen). I think the new setup screen is a nice convenience when someone is first starting up FDT, but it shouldnt try to force me to do anything other than pick which license. |
Show » |
|
However, your correct. This is a terrible bug. The SDK scanner should be accepting the location and not using a cached one.