Has anyone asked if the designer could be changed to allow the modification of variables passed so that the operator can evaluate the effect of those variables on the various objects (ie, in an appearance condition)?
For instance, we have a template that has three sets of two text bodies. A different body is shown depending on the value (1,2 or 3) of a variable called LTR_TYPE.
If you could manipulate this variable and check a box that activated the appearance conditions on preview, then you could see what each ‘type’ of document would look like.
Just thought I’d throw this in and see what came of it…
Well you can add menu items in the designer (using
LL_CMND_MODIFYMENU), so when the user selects them
(LL_CMND_SELECTMENU) you can change variables on-the-fly using
LlDefineVariable().
I do NOT know a good way to refresh the display after changing the
variable’s contents, though. You might need to find the designer
window to redraw (oops, there are multiple!) and send it an
WM_ERASEBKGND.
RedrawWindow(FindWindow(“L&LFrame1332”,NULL),NULL,NULL,RDW_ERASE|RDW_INVALIDATE|RDW_ALLCHILDREN)
might work, though this is overkill. Keep in mind FindWindow() might
find designer windows of other processes too, so check the process ID
(GetWindowThreadProcessId()) to make sure you have the correct one.
Paulchen
“Regan Cawkwell” <regan@rbau…> wrote in message
news:29962922008124851@combit.net…
Has anyone asked if the designer could be changed to allow the
modification of variables passed so that the operator can evaluate
the effect of those variables on the various objects (ie, in an
appearance condition)?
For instance, we have a template that has three sets of two text
bodies. A different body is shown depending on the value (1,2 or 3)
of a variable called LTR_TYPE.
If you could manipulate this variable and check a box that activated
the appearance conditions on preview, then you could see what each
‘type’ of document would look like.
Just thought I’d throw this in and see what came of it…
