You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the -width param acts very weird, its described as pixels unit, however if I set it to 450, I get an 18kx18k pixel image. If I specify 10, I get a 410x410 image, so I suspect there is some sort of mathematical shenanigans going on...
EDIT: thinking about it, it sounds like its acting like a multiplier rather than a static value...
The text was updated successfully, but these errors were encountered:
EDIT: thinking about it, it sounds like its acting like a multiplier rather than a static value...
Too bad that it takes an integer, then. Maybe we could get desired dimensions if we could supply a value between 0 and 1. :) The cmdlets validate width values 10-2000...
Any chance this will be updated to work "as advertised" (100 px by default, custom px dimensions using the Width parameter)?
the -width param acts very weird, its described as pixels unit, however if I set it to 450, I get an 18kx18k pixel image. If I specify 10, I get a 410x410 image, so I suspect there is some sort of mathematical shenanigans going on...
EDIT: thinking about it, it sounds like its acting like a multiplier rather than a static value...
The text was updated successfully, but these errors were encountered: