I create windows for a container and associated thread process in code on demand to permit multiple monitors of server-side tasks. I create and configure the window using this code:
WBackupJob.Append New WBackupWindow
Dim thisWindow As Integer = WBackupJob.Ubound
WBackupJob(thisWindow).Frame = Window.FrameTypeDocument
WBackupJob(thisWindow).MinimizeButton = True
WBackupJob(thisWindow).MenuBar = Nil
WBackupJob(thisWindow).MenuBarVisible = True
However, when the window is shown, the Minimize button is not displayed. I have verified that the window in the array is the correct window.
MinimizeButton and MaximizeButton properties are read only during runtime.
Other Read-Only Properties here:
Some have no effect after the window is constructed. The frame type is not changeable at runtime like this.
Understood - so in order to achieve what I need, I need to create the window template in the IDE and then create each new instance as a new copy of that template window.
Some have no effect unless RESIZEABLE is also selected as true
So that begs another question - why isn’t this flagged at compile time?
Because it’s not a compile error - it just has no effect.
Actually, it has an affect in that the developer is thinking they’ve done the right thing, but the running app says otherwise. In fact, any read-only property should raise a compiler error if it is being set in code.
self.isresizable = me.value <> 0//me is a pagepanel
With this code in the action event of a pagepanel, the maximizebutton gets grayed out when the panel’s value is 0, and it gets green when the panel’s value is <> 0.