-
-
Notifications
You must be signed in to change notification settings - Fork 282
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Mac]: Solar2D periodically installs plugins - can we control when this takes place? #479
Comments
There are several different ways of approaching this, some of which would be relatively trivial. The plugin fetch occurs in: platform/resources/shell.lua. The "once a day" thing you're referring to occurs here: corona/platform/resources/shell.lua Lines 372 to 380 in 2ed91b2
Forcing a plugin version won't have any impact on this as plugins of particular versions can receive bug fixes, etc. However, adding a general property to build.settings to "not check for plugin updates" would be relatively trivial to implement. Adding plugin specific properties to control the updates for each individual plugin probably wouldn't be much of a stretch either. I think we could take one extra step here as well and consider adding some minor UI to inform the user that the plugin is in fact fetching plugin updates. I'm a fairly experienced user and I only realised the lag spikes on launch were caused by plugins being fetched like 2 years ago. I could take a look at this issue around Thursday or Friday next week. |
Thanks @XeduR Maybe we can add one more option to each plugin definition (See #426) ["CoronaProvider.native.popup.quickLook"] = {
publisherId = "com.coronalabs",
version = "^1.2.5",
autoUpdate = false
} I suppose Or we could have a global setting in build.settings, |
I think I’ll just make maxAge customizable. This would be easy fix for the issue. Syntax for disabling auto-update for me seem quite ambiguous. May be it would be easier to deal with the issue with a setting? |
Making the maxAge customisable was my idea as well for the general approach as well. I figured it'd be quick to assign values like:
|
This should be fixed by #480. To customize the timer, run a command: defaults write com.coronalabs.Corona_Simulator SimPluginCacheMaxAge -int 0 0 or less - disables timer. defaults delete com.coronalabs.Corona_Simulator SimPluginCacheMaxAge On windows: reg ADD "HKEY_CURRENT_USER\Software\Ansca Corona\Corona Simulator\Preferences" /f /v SimPluginCacheMaxAge /d 5
rem And to delete:
reg DELETE "HKEY_CURRENT_USER\Software\Ansca Corona\Corona Simulator\Preferences" /f /v SimPluginCacheMaxAge |
Describe the bug
About once a day, when Solar2D starts up it takes about 10 seconds to check all plugins.
Can we stop this default behaviour, and only check plugins when we ask it to?
If we use this #427 then will it prevent this happening, or will it still check?
Target platform and where build was made:
To Reproduce
Start up Solar2D simulator. See log something like below
The text was updated successfully, but these errors were encountered: