You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Profiles named JOB or NAME_JOB will be checked for on job changes.
However I don't believe this functions at all. The job change hook uses name to load the configuration instead of name_short as I would expect it to, but even with this fix, the configuration does not load or save.
windower.register_event('job change',function(job)
if load_profile(res.jobs[job].name) then
I would expect job based configurations to behave as overrides to the default settings, and defaults should be repplied when changing from those jobs with profiles applied back to another, but I don't believe this happens either.
Saving settings using //du save xxx only ever creates an empty xml node named xxx.
The text was updated successfully, but these errors were encountered:
As per the README:
Profiles named JOB or NAME_JOB will be checked for on job changes.
However I don't believe this functions at all. The job change hook uses
name
to load the configuration instead ofname_short
as I would expect it to, but even with this fix, the configuration does not load or save.I would expect job based configurations to behave as overrides to the default settings, and defaults should be repplied when changing from those jobs with profiles applied back to another, but I don't believe this happens either.
Saving settings using //du save xxx only ever creates an empty xml node named xxx.
The text was updated successfully, but these errors were encountered: