Thank You for your continued support and contributions!
It may also sometimes be necessary to restart the device after building the database for the changes to be committed.
Yeah, I am convinced part of the problem is the usual glitches with flash-mods and writing to disk.
In terms of what the underlying code actually says, when you select 'load database to RAM', at what point does it in fact_do_ that? Is it supposed to do it immediately you select the option, or is it deferred in some way, till something triggers it to happen?
Quote from: chris_s on May 10, 2022, 01:53:47 AM It may also sometimes be necessary to restart the device after building the database for the changes to be committed.For whatever reason, neither rebooting (i.e. holding centre button+menu) nor restarting (holding play till it shuts down then starting up again) seems to reliably cause that 'database cache' to activate.
In theory you shouldn't have to do anything but wait (after rebooting) for the cache to load – no idea what's going on there. Re fixed.cfg – I'm only barely aware of that functionality. Seems useful, but shouldn't it still remember the context plugin after a reboot, even if some other setting get reset to the values specified in fixed.cfg?
I still have some work to do with the openplugins module its independent of the cfg file but is keyed to langids so when the lang file changes it breaks the core ones its nothing major or dangerous just annoying but I haven't decided on a better way yet probably just an export function and better versioning Id hash language stings but it breaks when switching languages then.Setting the context plugin is immediate but it won't get saved permanantely unless you do a safe shutdown or leave it on long enough that the device decides to flush to disk and it saves to a temp file first like the cfg files do on flash devices
Page created in 0.037 seconds with 16 queries.