FanZoneExhaust schedule fields disabled in App for objects created with API

[MatthewSteen]

Issue overview

FanZoneExhaust objects created with the API have two schedule fields disabled in the App. Objects added to a model in the App are fine. Found in 2.9.0, but I assume it's present in newer versions based on a quick look at git blame. NatLabRockies/OpenStudio#4116

Current Behavior

Expected Behavior

Steps to Reproduce

require 'openstudio'
include OpenStudio::Model
m = Model.new
tz = ThermalZone.new(m)
fze = FanZoneExhaust.new(m)
fze.addToThermalZone(tz)
m.save

2. Open model and add FanZoneExhaust to zone with an object from the library

Possible Solution

Details

Environment

Some additional details about your environment for this issue (if relevant):

• Platform (Operating system, version): Windows 10
• Version of OpenStudio (if using an intermediate build, include SHA): 2.9.0

Context

[jmarrec]

Either:

• OpenStudio changes it's Constructor just to please the OSApp and initializes this field, which makes no sense now post-separation of SDK and App (hence why I closed the original FanZoneExhaust schedule fields disabled in App for objects created with API NatLabRockies/OpenStudio#4116) , but which is the way we've always handled that stuff in the past
• You ensure you initialize these fields (workaround)
• Or, we change the overall InspectorGadget behavior to deal with defaulted / uninitialized fields. We could add a flag in OpenStudioPolicy.xml to force display some fields perhaps.