For reasons unexplained I never get any grids on start-up on the LayoutWindow and it does not matter in what state I have saved or exited the program last time.
I mentioned above that a new Scene object defaults to having the grids turned off. I think it's been like that as long as AOI has existed.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I think it's been like that as long as AOI has existed.
I seem to remember that it could have been at least somehow different at some point... Like remembering in a file what setting it had the last time, but probably it's just me hoping it would have.... Or could it have been Troy's / somebody else's plugin that kept the setting?
Anyway, here's what my current development version of DisplayModeIcons looks like. I think I could add some user-defaults there (and maybe try to see that it wouldn't get into fight with any other plugin working on the same settings).
(BTW, the DMI on the server is not the latest I have sent on the forum. It is not entirely compatible with the current AoI )
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
TTools could very well have set that on SCENE_WINDOW_CREATED. In fact, I think you might be right.
ere's what my current development version of DisplayModeIcons looks like.
Did you intend to attach something there?
I think I could add some user-defaults there (and maybe try to see that it wouldn't get into fight with any other plugin working on the same settings).
I'd think that the better solution would be to save this correctly on the scene/defaults end, just to prevent the potential fighting.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
And on the original subject: I think I got the SPManager issue fixed.
It was due to some server changes that sourceforge made a while back. Actual changes are only two lines of code in the SPManager, and some tweaks to a file on the server.
Please try the attached, and see if they work for you.
Please try the attached, and see if they work for you.
Who should try it, me, or the one that maintains the files on the server? 🤔
If I should do the trying, where do I place the files or do I use the script from a command line?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
You. :) Put them in your ArtOfIllusion/Plugins folder and make sure that the new ones are the only copies. Then restart AoI and try if you can download from the server through AoI, this should fix that. (See Maxim's result below... It'd probably be very interesting if you had the same behavior.)
I'll test a bit later. (...time zone & workin hours)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Same as Maxim: First time it fails and I have to close the same pop-up note 4 time (one for each directory, I guess...). After rescan files are found.
Attached errors from SystemOut. Something from SPM and something from something else (What unknown Windows 10? It's the same one as before and as up to date as MS has felt appropriate.)
I thought I'd patched around that. Does it repeat on a restart? If so, please delete the .spmanagerprefs file from your user directory and try again.
Unknown windows version: That's not from AOI core code. The stack is from jinput, so I'm thinking that you are running the HIDPlugin? Very old version there, and a case where up-to-date system drivers may make a difference.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
First time I tried the scan, it did the popup note errors, then after dismissing those, I told it to rescan and then it all worked and the plugins updated correctly. 👍 🖖
I have more questions about AOI so I will start new threads for those.
Last edit: pencilart 2023-01-13
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Removing .spmanagerprefs (from 2014) took care of the scanning problem but then loading did not start. After yet another restart it seems to be working.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Made another tweak to the SPManager code: This build now puts the .spmanagerprefs file in the standard .artofillusion/ preferences folder, rather than directly in the user's home directory. Since I'm working on the code anyway, this seems like a good time to do it.
It does work around the "Need to delete the old file" issue, at the expense of leaving that old file orphaned. I think that it will be a smoother experience for the average user. Thoughts?
Luke's "Need to delete the old file issue" means the .spmanagerprefs file in your C: \Users[you]\ That old settings file caused the fail-at-first-attempt-thing. This latest version wrote its own in a new place, so the one you find there does not really hurt but is not used either.
I'm actually a little bit wondering why the SPManager could not delete/rewrite/update the old file itself, when changes were made? ... Or if it writes the file only once, then why does it write it at all? Obviously it knows all it need to know by some other means?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm actually a little bit wondering why the SPManager could not delete/rewrite/update the old file itself, when changes were made?
It (sort of) does. The prefs file contains the URL of the repository that has been most recently set in the SPMSetupFrame settings dialog, and by default uses that. You can get it to overwrite the old file by opening the dialog and deliberately saving/reverting some of the repo/proxy settings. (it gets the list of valid repos from another URL that I updated) I just didn't want to try to walk the entire user base through something that kludgy. (Trust me, I do enough walk-through customer support on my day job.)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
And, on further thought, I decided that it wouldn't be a bad idea to actually clean up after ourselves. New version has been posted as an announcement, and the code is on github for review.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I mentioned above that a new
Sceneobject defaults to having the grids turned off. I think it's been like that as long as AOI has existed.I seem to remember that it could have been at least somehow different at some point... Like remembering in a file what setting it had the last time, but probably it's just me hoping it would have.... Or could it have been Troy's / somebody else's plugin that kept the setting?
Anyway, here's what my current development version of
DisplayModeIconslooks like. I think I could add some user-defaults there (and maybe try to see that it wouldn't get into fight with any other plugin working on the same settings).(BTW, the DMI on the server is not the latest I have sent on the forum. It is not entirely compatible with the current AoI )
TTools could very well have set that on
SCENE_WINDOW_CREATED. In fact, I think you might be right.Did you intend to attach something there?
I'd think that the better solution would be to save this correctly on the scene/defaults end, just to prevent the potential fighting.
And on the original subject: I think I got the SPManager issue fixed.
It was due to some server changes that sourceforge made a while back. Actual changes are only two lines of code in the SPManager, and some tweaks to a file on the server.
Please try the attached, and see if they work for you.
Who should try it, me, or the one that maintains the files on the server? 🤔
If I should do the trying, where do I place the files or do I use the script from a command line?
You. :) Put them in your ArtOfIllusion/Plugins folder and make sure that the new ones are the only copies. Then restart AoI and try if you can download from the server through AoI, this should fix that. (See Maxim's result below... It'd probably be very interesting if you had the same behavior.)
I'll test a bit later. (...time zone & workin hours)
SPManager fails for me at first scan but begins to work after I invoke Rescan
Same as Maxim: First time it fails and I have to close the same pop-up note 4 time (one for each directory, I guess...). After rescan files are found.
Attached errors from SystemOut. Something from SPM and something from something else (What unknown Windows 10? It's the same one as before and as up to date as MS has felt appropriate.)
Rescan thing:
I thought I'd patched around that. Does it repeat on a restart? If so, please delete the
.spmanagerprefsfile from your user directory and try again.Unknown windows version: That's not from AOI core code. The stack is from jinput, so I'm thinking that you are running the HIDPlugin? Very old version there, and a case where up-to-date system drivers may make a difference.
First time I tried the scan, it did the popup note errors, then after dismissing those, I told it to rescan and then it all worked and the plugins updated correctly. 👍 🖖
I have more questions about AOI so I will start new threads for those.
Last edit: pencilart 2023-01-13
Removing .spmanagerprefs (from 2014) took care of the scanning problem but then loading did not start. After yet another restart it seems to be working.
Made another tweak to the SPManager code: This build now puts the
.spmanagerprefsfile in the standard.artofillusion/preferences folder, rather than directly in the user's home directory. Since I'm working on the code anyway, this seems like a good time to do it.It does work around the "Need to delete the old file" issue, at the expense of leaving that old file orphaned. I think that it will be a smoother experience for the average user. Thoughts?
See also https://github.com/ArtOfIllusion/SPManager/pull/10
Seems to be working. Scanned for plugins just fine.
I had removed the previous version before placing them into the plugins folder though.
Luke's "Need to delete the old file issue" means the .spmanagerprefs file in your C: \Users[you]\ That old settings file caused the fail-at-first-attempt-thing. This latest version wrote its own in a new place, so the one you find there does not really hurt but is not used either.
I'm actually a little bit wondering why the SPManager could not delete/rewrite/update the old file itself, when changes were made? ... Or if it writes the file only once, then why does it write it at all? Obviously it knows all it need to know by some other means?
It (sort of) does. The prefs file contains the URL of the repository that has been most recently set in the
SPMSetupFramesettings dialog, and by default uses that. You can get it to overwrite the old file by opening the dialog and deliberately saving/reverting some of the repo/proxy settings. (it gets the list of valid repos from another URL that I updated) I just didn't want to try to walk the entire user base through something that kludgy. (Trust me, I do enough walk-through customer support on my day job.)And, on further thought, I decided that it wouldn't be a bad idea to actually clean up after ourselves. New version has been posted as an announcement, and the code is on github for review.