RE: LPub3D 2.0 Released
2016-12-09, 12:48 (This post was last modified: 2016-12-09, 12:50 by Merlijn Wissink.)
2016-12-09, 12:48 (This post was last modified: 2016-12-09, 12:50 by Merlijn Wissink.)
(2016-12-09, 10:01)Trevor Sandy Wrote:(2016-12-09, 9:26)Merlijn Wissink Wrote: ...callout in a callout doesn't look very well :
I don't know what's happening here, but it sure isn't what it's supposed to do. Any ideas?
I didn't know nested callouts were possible in LPub3D or LPub for that matter
I certainly haven't released any functionality of the sort; furthermore, the legacy LPub code suggest this behaviour is explicitly forbidden.
Code:// This is what's supposed to happen when a callout [begin] meta is encountered.
case CalloutBeginRc:
if (callout) {
parseError("Nested CALLOUT not allowed within the same file",current);
} else {
callout = new Callout(curMeta,view);
callout->setTopOfCallout(current);
}
break;
Did the behaviour you expected exist on any earlier version of the software?
It would be interesting to see an example of the LPub meta pattern you used in the model file to produce nested callouts.
Cheers,
I'd swear I've seen callouts in callouts in the past. But, I couldn't quickly find an example. Now I start to doubt myself
Still, I can 'remember' it so clearly: the red box inside the yellow box; callout in a callout. I'll browse through some more instructions, see if I can find something like that anywhere. Maybe my mind is just plain wrong...
How I produced it: I'm not 100% sure (my memory is not... great ), but I believe I just created a callout from the 'parent' callout. Then I saw that little square and I realized the submodel in the parent also used a callout. I thought I needed to create the child-callout first, so I pressed undo, went to the child-submodel, transformed that into a callout (the child-callout) and then transformed the parent submodel back into a callout (parent callout). Still, just a little square.