Matthew Harrison Posted August 12, 2010 Report Share Posted August 12, 2010 Steps to reproduce: 1. Choose File->Open Package(s) from the File menu 2. Select a single package (.ogp) Expected Behavior: VIPM should add the package to the list of available packages Observed Behavior: VIPM opens the Package Information window, and very briefly displays the package info (for maybe 1/4 of a second), as in the attached image Then the Package Information window blanks out, as in the attached image The package is not added to the list. Workaround: Always select at least 2 packages when Opening Packages Link to comment Share on other sites More sharing options...
Jim Kring Posted August 13, 2010 Report Share Posted August 13, 2010 Hi Matthew, It was great seeing you and the MGI gang at NIWeek 2010! When you "open" a single package in VIPM 2010, it doesn't add the package to the VIPM package list -- it opens the Package Info Dialog. This is the designed behavior. Then, if you install the package it will appear in the package list. However, it seems that you've found a bug that's preventing the package info from actually appearing in the Package Info Dialog. That's strange. Are you able to reproduce the problem or did it just happen once? Thanks, Link to comment Share on other sites More sharing options...
Michael Aivaliotis Posted August 13, 2010 Report Share Posted August 13, 2010 Please submit your VIPM error log. Follow instructions here. Link to comment Share on other sites More sharing options...
Matthew Harrison Posted August 13, 2010 Author Report Share Posted August 13, 2010 Hi Matthew, It was great seeing you and the MGI gang at NIWeek 2010! When you "open" a single package in VIPM 2010, it doesn't add the package to the VIPM package list -- it opens the Package Info Dialog. This is the designed behavior. Then, if you install the package it will appear in the package list. However, it seems that you've found a bug that's preventing the package info from actually appearing in the Package Info Dialog. That's strange. Are you able to reproduce the problem or did it just happen once? Thanks, It was really, really great to see you as well. Thanks so much for putting on that great BBQ. I did not realize that the Package Info Dialog was expected behavior. I should note, however, that if multiple packages are selected, it does not come up. Instead, I get a dialog like the attached: It is very reproducible. Just select a single package to add. I do not see it with the ones that automatically download from the package servers. Michael asked for an error log, so I'll post to that message with a fresh error from this morning. Best Wishes, Matthew Harrison Link to comment Share on other sites More sharing options...
Matthew Harrison Posted August 13, 2010 Author Report Share Posted August 13, 2010 Please submit your VIPM error log. Follow instructions here. Here is the error log from this morning after a single attempt to Open a single package. It appears to be complaining about file permissions, but I don't see any file permission problems, and like I said, these packages install fine as long as you select more than one. -Matt August_13_2010.txt Link to comment Share on other sites More sharing options...
Jim Kring Posted August 13, 2010 Report Share Posted August 13, 2010 Hey Matt, I did not realize that the Package Info Dialog was expected behavior. I should note, however, that if multiple packages are selected, it does not come up. Instead, I get a dialog like the attached: Yes, this is expected, too. If you try to open multiple packages, we assume you're wanting add them to your package list or install them all. Sorry if this isn't the most intuitive/expected behavior. Here is the error log from this morning after a single attempt to Open a single package. It appears to be complaining about file permissions, but I don't see any file permission problems, and like I said, these packages install fine as long as you select more than one. My guess about the permission issue is that the file ("C:\Users\Matthew\AppData\Local\Temp\icon.bmp") is read-only. Can you please confirm? Can you attach your package file (or email it to customer-service@jki.net) so that we can take a look and try to reproduce this? Thanks, Link to comment Share on other sites More sharing options...
Matthew Harrison Posted August 13, 2010 Author Report Share Posted August 13, 2010 Hey Matt,Yes, this is expected, too. If you try to open multiple packages, we assume you're wanting add them to your package list or install them all. Sorry if this isn't the most intuitive/expected behavior. My guess about the permission issue is that the file ("C:\Users\Matthew\AppData\Local\Temp\icon.bmp") is read-only. Can you please confirm? Can you attach your package file (or email it to customer-service@jki.net) so that we can take a look and try to reproduce this? Thanks, Ah, you are brilliant, Jim. Resetting the Read-only attribute on this file in the temp directory will fix the problem. The key discovery for me was that deleting the file causes the problem to reappear, so I checked into our package, and there are a few files (the icon among them) that are built into the package with the read-only flag set. So, we need to make sure that all of the files destined for the package get the read-only flag cleared before we build the package. Very impressive remote debugging- many, many thanks. Best Wishes, Matthew Harrison Link to comment Share on other sites More sharing options...
Jim Kring Posted August 13, 2010 Report Share Posted August 13, 2010 Ah, you are brilliant, Jim. Resetting the Read-only attribute on this file in the temp directory will fix the problem. The key discovery for me was that deleting the file causes the problem to reappear, so I checked into our package, and there are a few files (the icon among them) that are built into the package with the read-only flag set. So, we need to make sure that all of the files destined for the package get the read-only flag cleared before we build the package. Very impressive remote debugging- many, many thanks. Best Wishes, Matthew Harrison Hey Matt, I'm very glad we figured out the problem (icon.bmp was read-only) and that a work-around (ensuring all the package source files are writable before packaging) is feasible for you I'll file a bug on this, so that VIPM better handles packages containing read-only files. -Jim Link to comment Share on other sites More sharing options...
Jim Kring Posted August 13, 2010 Report Share Posted August 13, 2010 One more thing, Matt... I assume that this package was not built using VIPM 2010 (since VIPM 2010 builds the icon.bmp file dynamically and it should never be read-only). You should really try (re)building your package in VIPM 2010 -- it's pretty awesome Link to comment Share on other sites More sharing options...
Matthew Harrison Posted August 13, 2010 Author Report Share Posted August 13, 2010 One more thing, Matt... I assume that this package was not built using VIPM 2010 (since VIPM 2010 builds the icon.bmp file dynamically and it should never be read-only). You should really try (re)building your package in VIPM 2010 -- it's pretty awesome Yes, we are still using the older tools, but we are working this month on getting switched over. Thanks for the great tools. -Matt Link to comment Share on other sites More sharing options...
Jim Kring Posted August 13, 2010 Report Share Posted August 13, 2010 Yes, we are still using the older tools, but we are working this month on getting switched over. Thanks for the great tools. -Matt That's great to hear. We're looking forward to your feedback. Link to comment Share on other sites More sharing options...
Jim Kring Posted November 2, 2010 Report Share Posted November 2, 2010 Hi There. Just a quick update. This bug should be fixed in VIPM 2010.0.1 -- you can find more info in the release notes, here: http://jki.net/vipm/release-notes Thanks! -Jim Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.