bb.donnay-software.com

Never noticed this class

It came four years ago. And it didn't work well at the beginning.

Old age creeping in

Never mind.

Take a look at the VirtualScreen class(object) of Xbase++ (2.0). VirtualScreen():getPhysicalScreenCount() returns the number of physical screens attached to the workstation.

If you want to stay with this architecture, place all buttons possible (even on top of each other) and use the HIDE clause to not show those you don't need depending on the selection on the left. Change the value for the condition there (like HIDE {||nMenuItem # 1}), fire "DC_GetRefresh(oArea)" to s...

I think it's much simpler. He wants to actualize the items (DCPUSHBUTTONXPs) on the right hand side of the "Productos Consultados"-dialog depending on the button clicked on the left side.

And I never used this. I even can't find it in the docs.

And maybe it's not created because the bundle was locked.

I don't find the Method "UnlockComponent" in the docs für "MailMan". However, we only use the Global object for unlocking the bundle.

I suppose that unlocking at the start of the application isn't valid when starting functions in another thread. I can't confirm this. Whereever I unlocked Chilkat and where-else-ever I call for the unlockStatus, it's not zero. Seems like it even survives restarting the app. 🤔 Edit: This is what the...

We use the unlock mechanism once within every routine that uses Chilkat. Unlocking takes almost no time. You are still using version 9.5.0?