When using the context menu on an assembly being rendered with LDView and selecting the menu item "Add LDView Assembly Rendered Arguments", the first argument entered is conflated with the immediately prior argument when LDView is invoked. This leads to unpredictable renderer behaviour.
For example, the LDView command line arguments ModelSize and ModelCenter can be used to zoom and crop an image. But when the first argument is conglated to the prior argument, the desired parameter is not passed to LDView.
The first screen shot illustrates the desired image cropping, which was achieved by inserting extra "noise" parameter values:
with the invoking of the LDView process and its argument being:
However, when invoked without the "niose" parameters on the next page, the desired rendering does not result:
the conflation of the first user supplied LDView argument can be seen in the process invocation.:
Environment
Version of LPub3D - Release 2.4.6 Revision 363 Build 3474
Operating system - Windows 10, x86_64
Steps to reproduce
The mpd in the attached zip file contains a model displaying this behaviour.
Open the model, navigate to page 3 and then page 4. Page 3 is rendered as expected, page 4 is not.
Subject
When using the context menu on an assembly being rendered with LDView and selecting the menu item "Add LDView Assembly Rendered Arguments", the first argument entered is conflated with the immediately prior argument when LDView is invoked. This leads to unpredictable renderer behaviour.
For example, the LDView command line arguments ModelSize and ModelCenter can be used to zoom and crop an image. But when the first argument is conglated to the prior argument, the desired parameter is not passed to LDView.
The first screen shot illustrates the desired image cropping, which was achieved by inserting extra "noise" parameter values:![p3_zoomed](https://github.com/trevorsandy/lpub3d/assets/37604323/6013c70d-735c-4763-a21d-6aa1b3c85710)
with the invoking of the LDView process and its argument being:
However, when invoked without the "niose" parameters on the next page, the desired rendering does not result:![p4_not_zoomed](https://github.com/trevorsandy/lpub3d/assets/37604323/092b1b5c-1622-4068-8947-477ed095d5fa)
the conflation of the first user supplied LDView argument can be seen in the process invocation.:![p4_ldview_invoke](https://github.com/trevorsandy/lpub3d/assets/37604323/92a44e7c-7846-4b1e-af16-319f15244821)
Environment
Steps to reproduce
The mpd in the attached zip file contains a model displaying this behaviour. Open the model, navigate to page 3 and then page 4. Page 3 is rendered as expected, page 4 is not.
ldview_args.zip
Expected behaviour
All the user supplied additional arguments should be passed to LDView.
Actual behaviour
The first user supplied argument is being conflated to the immediately prior LPub3D generated argument.
Workaround
Set the first parameter in the dialog to serve as a "noise" argument to the remaining arguments are passed successfully.
Solution suggestion
When user arguments for LDView are supplied, prepend a space to the front of the user argument list and don't trim it.