I have some sheets, with some sheet models.when I try to print, the sheet boundary is not recognized,it is grayed out in the printerdialogbox
the models are all defined as sheetshow to make the sheet boundary to be regognized by the pltcfg
Please advise on the Product / version being used to help others answer your query,
That said I suspect that the issue relates to the Sheet Models Custom Size specifically the 'Width having a Negative value of -600. Assuming this is only affecting Sheet Models having negative values.
Extract from your image.
Related Wiki :
(+) The sheet model option in the print dialog box -> General Settings -> Area is grey out. - Printing and Plotting Wiki - Printing and Plotting - Bentley Communities
MISSING RESOURCE: VerifiedBy RikR
very strange, the X-and Y-values must be positive numbers,every "integer" can be positive or negativewhy should the negative value give an internal error?
good to know, but this can rather be fixed
btw (my product: OBD u9.2 = Open Building Designer update 9.2)
Because paper size is a number based on the size of the paper measured from the bottom left corner to the top right corner, always measured in the positive direction.
Yes, integers can technically be positive or negative, but certain measurement types follow specfic parameters and standards. There is no "negative width".
Power GeoPak 08.11.09.918Power InRoads 08.11.09.918OpenRoads Designer 2021 R2
Thanks for the detailed info,but it should be better to give a clear error while filling the negative value,now nothing is telling what is wrong, and the sheet is grayed outthis is not "fool prove"on bigger sheets the "header" is always placed on the right bottom corner.if this header is filled in, ore the sheet is duplicated, the height and width can be adapted while this header stays on place.now every thing has to movehaving a negative value for the sheet does not say the paper should be negative,it only says the sheet is measured from the origin to the leftthis reduces some unnecessary handlingregards Rik
You definitely have a point!
An error message might be helpful. Or some way to tell MicroStation to define from right-to-left. Or to mention this point in the Help somewhere. I don't know if this is strictly a MicroStation convention, or a Windows convention.