It was not v 254.1 but v 201 that I saw this phenomenon.
Excuse me.
In v 254.1, the value of “CurrentLayoutId” is not set in the Schedule class (Always remain at 0), so (1) in the previous post does not occur.
This is because the following “CurrentLayoutId” settings in v 201 do not exist in v 254.1:.
(Schedule.cs)
/// '<'summary'>'
/// The current layout id
/// '<'/summary'>'
public int CurrentLayoutId
{
get
{
return _currentLayoutId;
}
set
{
_currentLayoutId = value;
if (_scheduleManager != null)
_scheduleManager.CurrentLayoutId = _currentLayoutId;
}
}
private int _currentLayoutId;
As a result, my next post
will be
because the following if statement is always false:.
(ScheduleManager.cs)
if (!ApplicationSettings.Default.ExpireModifiedLayouts && layout.id == CurrentLayoutId)
{
Trace.WriteLine(new LogMessage("ScheduleManager - LoadNewSchedule", "Skipping validity test for current layout."), LogType.Audit.ToString());
}
As a result, in our case (v 254.1),
Instead of a splash screen caused by an invalid layout being incorrectly treated as valid,
As a result, the default layout is displayed.