I just noticed that when editing a PBForms app that the statement which I had inserted after DIALOG NEW was discarded. In fact this was a macro including a setprop statement, the purpose of which was to pass a value from the dialog proc to the callback proc, which the callback could pick up in its WM_INITDIALOG handler.
Is there any setting or strategy by which I can talk PBForms into not doing this.
If not, from a design point of view, would it not be better to alllow "user code" to be inserted between the DIALOG NEW and CONTROL ADD statements? It's not like code between the CONTROL ADD statements which might get lost in shuffling the z-order.
Is there any setting or strategy by which I can talk PBForms into not doing this.
If not, from a design point of view, would it not be better to alllow "user code" to be inserted between the DIALOG NEW and CONTROL ADD statements? It's not like code between the CONTROL ADD statements which might get lost in shuffling the z-order.
Comment