Thermo appear to be keeping the "Regular Method" type around only for backward compatibility. Skyline method export uses a Thermo provided API that supports only the "EZ Method" type. Like Waters transition list and method export, this means Skyline requests the run duration for unscheduled methods.

The default behavior for the Thermo transition lists should also be made the "EZ Method" case, though it should probably still be possible to get "Regular Method" format. Skyline should, however, display an error message when you try to export optimization transitions to the "Regular Method" format.

Hopefully, this will reduce the likelihood of Skyline users encountering the pitfalls associated with using the older "Regular Method" type.

Thermo Quantiva format is completely different, and no one has really complained about this.