The method used to "set the pixels to full pixels values" might matter.
Snapping nodes or bounding box corners to the grid works well and keeps the nodes / paths with integer stroke width aligned to the pixel grid [1]. There are however some known issues when changing the position or dimensions of a selection by entering numeric values in the entry fields on the select tool controls bar (or in the 'Transform…' dialog): for example a precise value might only stick after entering it three or more times; or changing the width or length (of horizontal or vertical lines) also effects the x and y coordinate.
[1] the concept of what snaps to what is important, as well as the type of bounding box used (Visual -- default, includes stroke width, or Geometric). A rectangle with a stroke width of 1 px node-snapped to the grid is still anti-aliased on export to PNG because each edge of the stroke is 0.5 px offset from the path centerline and the rendered path not aligned with the pixel grid.
The method used to "set the pixels to full pixels values" might matter.
Snapping nodes or bounding box corners to the grid works well and keeps the nodes / paths with integer stroke width aligned to the pixel grid [1]. There are however some known issues when changing the position or dimensions of a selection by entering numeric values in the entry fields on the select tool controls bar (or in the 'Transform…' dialog): for example a precise value might only stick after entering it three or more times; or changing the width or length (of horizontal or vertical lines) also effects the x and y coordinate.
[1] the concept of what snaps to what is important, as well as the type of bounding box used (Visual -- default, includes stroke width, or Geometric). A rectangle with a stroke width of 1 px node-snapped to the grid is still anti-aliased on export to PNG because each edge of the stroke is 0.5 px offset from the path centerline and the rendered path not aligned with the pixel grid.