Different dimensions with shift and xshift












5















I discovered that there is a different default dimension in shift and xshift.



Consider the following mwe



documentclass{article}

usepackage{tikz}

begin{document}

begin{tikzpicture}

  node (a) at (0,3) {a};

  node (b) at (0,2) {b};

  node (c) at (0,1) {c};

  node (d) at (0,0) {d};

  node[xshift=5cm] at (a) {aa};

  node[shift={(5cm,0)}] at (b) {bb};

  node[xshift=5] at (c) {cc};

  node[shift={(5,0)}] at (d) {dd};

  draw[help lines] (0,0) grid (5,3) ;

end{tikzpicture}

end{document}


It gives the following result:
enter image description here



For the two first lines given with 'cm' (a and b), the behavior of shift and xshift is the same.



But without dimensions (c and d) , it seems that shift uses default tikz dimensions, while xshift seems to use point?



I noticed that in the manual xshift is always given with cm, but this behavior is not explained.



Am I doing something incorrect? Is it a bug or a feature?






tikz-pgf







share|improve this question


















  • 1





    You're not doing anything incorrect, and this has been noticed before. Another situation in which the default unit is cm is a cricle, so draw (0,0) circle(1); gives you a circle of radius 1cm, similarly for arcs. As you have noticed, this is also true for coordinates, so at (1,0) and at (1cm,0) are equivalent. That's why the shift={(5,0)} and shift={(5cm,0)} can be used interchangedly. But for "most" other situations the default unit is pt.

    – marmot
    2 hours ago













  • I can understand that commands doing completely different actions have different default dimensions. But shift and xshift seem very close, at least in terms of functionality. And this difference in behavior is really confusing...

    – Alain Merigot
    2 hours ago













  • I agree it is confusing. But in my list of confusing things this is below the confusion which library one has to load to make an example from the pgfmanual run through. (And I would like to draw your attention to this source of confusion, which confuses me, too. ;-)

    – marmot
    2 hours ago
















5















I discovered that there is a different default dimension in shift and xshift.



Consider the following mwe



documentclass{article}

usepackage{tikz}

begin{document}

begin{tikzpicture}

  node (a) at (0,3) {a};

  node (b) at (0,2) {b};

  node (c) at (0,1) {c};

  node (d) at (0,0) {d};

  node[xshift=5cm] at (a) {aa};

  node[shift={(5cm,0)}] at (b) {bb};

  node[xshift=5] at (c) {cc};

  node[shift={(5,0)}] at (d) {dd};

  draw[help lines] (0,0) grid (5,3) ;

end{tikzpicture}

end{document}


It gives the following result:
enter image description here



For the two first lines given with 'cm' (a and b), the behavior of shift and xshift is the same.



But without dimensions (c and d) , it seems that shift uses default tikz dimensions, while xshift seems to use point?



I noticed that in the manual xshift is always given with cm, but this behavior is not explained.



Am I doing something incorrect? Is it a bug or a feature?






tikz-pgf







share|improve this question


















  • 1





    You're not doing anything incorrect, and this has been noticed before. Another situation in which the default unit is cm is a cricle, so draw (0,0) circle(1); gives you a circle of radius 1cm, similarly for arcs. As you have noticed, this is also true for coordinates, so at (1,0) and at (1cm,0) are equivalent. That's why the shift={(5,0)} and shift={(5cm,0)} can be used interchangedly. But for "most" other situations the default unit is pt.

    – marmot
    2 hours ago













  • I can understand that commands doing completely different actions have different default dimensions. But shift and xshift seem very close, at least in terms of functionality. And this difference in behavior is really confusing...

    – Alain Merigot
    2 hours ago













  • I agree it is confusing. But in my list of confusing things this is below the confusion which library one has to load to make an example from the pgfmanual run through. (And I would like to draw your attention to this source of confusion, which confuses me, too. ;-)

    – marmot
    2 hours ago














5












5








5








I discovered that there is a different default dimension in shift and xshift.



Consider the following mwe



documentclass{article}

usepackage{tikz}

begin{document}

begin{tikzpicture}

  node (a) at (0,3) {a};

  node (b) at (0,2) {b};

  node (c) at (0,1) {c};

  node (d) at (0,0) {d};

  node[xshift=5cm] at (a) {aa};

  node[shift={(5cm,0)}] at (b) {bb};

  node[xshift=5] at (c) {cc};

  node[shift={(5,0)}] at (d) {dd};

  draw[help lines] (0,0) grid (5,3) ;

end{tikzpicture}

end{document}


It gives the following result:
enter image description here



For the two first lines given with 'cm' (a and b), the behavior of shift and xshift is the same.



But without dimensions (c and d) , it seems that shift uses default tikz dimensions, while xshift seems to use point?



I noticed that in the manual xshift is always given with cm, but this behavior is not explained.



Am I doing something incorrect? Is it a bug or a feature?






tikz-pgf







share|improve this question














I discovered that there is a different default dimension in shift and xshift.



Consider the following mwe



documentclass{article}

usepackage{tikz}

begin{document}

begin{tikzpicture}

  node (a) at (0,3) {a};

  node (b) at (0,2) {b};

  node (c) at (0,1) {c};

  node (d) at (0,0) {d};

  node[xshift=5cm] at (a) {aa};

  node[shift={(5cm,0)}] at (b) {bb};

  node[xshift=5] at (c) {cc};

  node[shift={(5,0)}] at (d) {dd};

  draw[help lines] (0,0) grid (5,3) ;

end{tikzpicture}

end{document}


It gives the following result:
enter image description here



For the two first lines given with 'cm' (a and b), the behavior of shift and xshift is the same.



But without dimensions (c and d) , it seems that shift uses default tikz dimensions, while xshift seems to use point?



I noticed that in the manual xshift is always given with cm, but this behavior is not explained.



Am I doing something incorrect? Is it a bug or a feature?






tikz-pgf




tikz-pgf






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 2 hours ago









Alain MerigotAlain Merigot

612




612








  • 1





    You're not doing anything incorrect, and this has been noticed before. Another situation in which the default unit is cm is a cricle, so draw (0,0) circle(1); gives you a circle of radius 1cm, similarly for arcs. As you have noticed, this is also true for coordinates, so at (1,0) and at (1cm,0) are equivalent. That's why the shift={(5,0)} and shift={(5cm,0)} can be used interchangedly. But for "most" other situations the default unit is pt.

    – marmot
    2 hours ago













  • I can understand that commands doing completely different actions have different default dimensions. But shift and xshift seem very close, at least in terms of functionality. And this difference in behavior is really confusing...

    – Alain Merigot
    2 hours ago













  • I agree it is confusing. But in my list of confusing things this is below the confusion which library one has to load to make an example from the pgfmanual run through. (And I would like to draw your attention to this source of confusion, which confuses me, too. ;-)

    – marmot
    2 hours ago














  • 1





    You're not doing anything incorrect, and this has been noticed before. Another situation in which the default unit is cm is a cricle, so draw (0,0) circle(1); gives you a circle of radius 1cm, similarly for arcs. As you have noticed, this is also true for coordinates, so at (1,0) and at (1cm,0) are equivalent. That's why the shift={(5,0)} and shift={(5cm,0)} can be used interchangedly. But for "most" other situations the default unit is pt.

    – marmot
    2 hours ago













  • I can understand that commands doing completely different actions have different default dimensions. But shift and xshift seem very close, at least in terms of functionality. And this difference in behavior is really confusing...

    – Alain Merigot
    2 hours ago













  • I agree it is confusing. But in my list of confusing things this is below the confusion which library one has to load to make an example from the pgfmanual run through. (And I would like to draw your attention to this source of confusion, which confuses me, too. ;-)

    – marmot
    2 hours ago








1




1





You're not doing anything incorrect, and this has been noticed before. Another situation in which the default unit is cm is a cricle, so draw (0,0) circle(1); gives you a circle of radius 1cm, similarly for arcs. As you have noticed, this is also true for coordinates, so at (1,0) and at (1cm,0) are equivalent. That's why the shift={(5,0)} and shift={(5cm,0)} can be used interchangedly. But for "most" other situations the default unit is pt.

– marmot
2 hours ago







You're not doing anything incorrect, and this has been noticed before. Another situation in which the default unit is cm is a cricle, so draw (0,0) circle(1); gives you a circle of radius 1cm, similarly for arcs. As you have noticed, this is also true for coordinates, so at (1,0) and at (1cm,0) are equivalent. That's why the shift={(5,0)} and shift={(5cm,0)} can be used interchangedly. But for "most" other situations the default unit is pt.

– marmot
2 hours ago















I can understand that commands doing completely different actions have different default dimensions. But shift and xshift seem very close, at least in terms of functionality. And this difference in behavior is really confusing...

– Alain Merigot
2 hours ago







I can understand that commands doing completely different actions have different default dimensions. But shift and xshift seem very close, at least in terms of functionality. And this difference in behavior is really confusing...

– Alain Merigot
2 hours ago















I agree it is confusing. But in my list of confusing things this is below the confusion which library one has to load to make an example from the pgfmanual run through. (And I would like to draw your attention to this source of confusion, which confuses me, too. ;-)

– marmot
2 hours ago





I agree it is confusing. But in my list of confusing things this is below the confusion which library one has to load to make an example from the pgfmanual run through. (And I would like to draw your attention to this source of confusion, which confuses me, too. ;-)

– marmot
2 hours ago










2 Answers
2






active

oldest

votes


















3














Some thoughts:




  • You're not doing anything incorrect.

  • Is it a bug? It is not a bug in the sense that the program crashes or that the result deviates from what one may expect from the manual. So my take it is not a bug.

  • The default unit for coordinates is cm, so at (1,0) and at (1cm,0) are equivalent. That's why the shift={(5,0)} and shift={(5cm,0)} can be used interchangedly.

  • Is this not the only situation where cm is the unit. Another situation in which the default unit is cm is a cricle, so draw (0,0) circle(1); gives you a circle of radius 1cm, similarly for arcs.

  • But for "most" other situations the default unit is pt.






share|improve this answer































    1














    In TikZ always the default unit for length values is pt. And we have




    /tikz/xshift=<dimension>




    So the default unit for xshift is pt.



    In (1,0) you can think of cm as default unit but there is no default unit. Simply (1,0) is 1.x+0.y so it depends on the value of the x vector, which is initially set to (1cm,0).






    share|improve this answer

























      Your Answer








      StackExchange.ready(function() {
      var channelOptions = {
      tags: "".split(" "),
      id: "85"
      };
      initTagRenderer("".split(" "), "".split(" "), channelOptions);

      StackExchange.using("externalEditor", function() {
      // Have to fire editor after snippets, if snippets enabled
      if (StackExchange.settings.snippets.snippetsEnabled) {
      StackExchange.using("snippets", function() {
      createEditor();
      });
      }
      else {
      createEditor();
      }
      });

      function createEditor() {
      StackExchange.prepareEditor({
      heartbeatType: 'answer',
      autoActivateHeartbeat: false,
      convertImagesToLinks: false,
      noModals: true,
      showLowRepImageUploadWarning: true,
      reputationToPostImages: null,
      bindNavPrevention: true,
      postfix: "",
      imageUploader: {
      brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
      contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
      allowUrls: true
      },
      onDemand: true,
      discardSelector: ".discard-answer"
      ,immediatelyShowMarkdownHelp:true
      });


      }
      });














      draft saved

      draft discarded


















      StackExchange.ready(
      function () {
      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f469893%2fdifferent-dimensions-with-shift-and-xshift%23new-answer', 'question_page');
      }
      );

      Post as a guest















      Required, but never shown

























      2 Answers
      2






      active

      oldest

      votes








      2 Answers
      2






      active

      oldest

      votes









      active

      oldest

      votes






      active

      oldest

      votes









      3














      Some thoughts:




      • You're not doing anything incorrect.

      • Is it a bug? It is not a bug in the sense that the program crashes or that the result deviates from what one may expect from the manual. So my take it is not a bug.

      • The default unit for coordinates is cm, so at (1,0) and at (1cm,0) are equivalent. That's why the shift={(5,0)} and shift={(5cm,0)} can be used interchangedly.

      • Is this not the only situation where cm is the unit. Another situation in which the default unit is cm is a cricle, so draw (0,0) circle(1); gives you a circle of radius 1cm, similarly for arcs.

      • But for "most" other situations the default unit is pt.






      share|improve this answer




























        3














        Some thoughts:




        • You're not doing anything incorrect.

        • Is it a bug? It is not a bug in the sense that the program crashes or that the result deviates from what one may expect from the manual. So my take it is not a bug.

        • The default unit for coordinates is cm, so at (1,0) and at (1cm,0) are equivalent. That's why the shift={(5,0)} and shift={(5cm,0)} can be used interchangedly.

        • Is this not the only situation where cm is the unit. Another situation in which the default unit is cm is a cricle, so draw (0,0) circle(1); gives you a circle of radius 1cm, similarly for arcs.

        • But for "most" other situations the default unit is pt.






        share|improve this answer


























          3












          3








          3







          Some thoughts:




          • You're not doing anything incorrect.

          • Is it a bug? It is not a bug in the sense that the program crashes or that the result deviates from what one may expect from the manual. So my take it is not a bug.

          • The default unit for coordinates is cm, so at (1,0) and at (1cm,0) are equivalent. That's why the shift={(5,0)} and shift={(5cm,0)} can be used interchangedly.

          • Is this not the only situation where cm is the unit. Another situation in which the default unit is cm is a cricle, so draw (0,0) circle(1); gives you a circle of radius 1cm, similarly for arcs.

          • But for "most" other situations the default unit is pt.






          share|improve this answer













          Some thoughts:




          • You're not doing anything incorrect.

          • Is it a bug? It is not a bug in the sense that the program crashes or that the result deviates from what one may expect from the manual. So my take it is not a bug.

          • The default unit for coordinates is cm, so at (1,0) and at (1cm,0) are equivalent. That's why the shift={(5,0)} and shift={(5cm,0)} can be used interchangedly.

          • Is this not the only situation where cm is the unit. Another situation in which the default unit is cm is a cricle, so draw (0,0) circle(1); gives you a circle of radius 1cm, similarly for arcs.

          • But for "most" other situations the default unit is pt.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered 1 hour ago









          marmotmarmot

          90.9k4104196




          90.9k4104196























              1














              In TikZ always the default unit for length values is pt. And we have




              /tikz/xshift=<dimension>




              So the default unit for xshift is pt.



              In (1,0) you can think of cm as default unit but there is no default unit. Simply (1,0) is 1.x+0.y so it depends on the value of the x vector, which is initially set to (1cm,0).






              share|improve this answer






























                1














                In TikZ always the default unit for length values is pt. And we have




                /tikz/xshift=<dimension>




                So the default unit for xshift is pt.



                In (1,0) you can think of cm as default unit but there is no default unit. Simply (1,0) is 1.x+0.y so it depends on the value of the x vector, which is initially set to (1cm,0).






                share|improve this answer




























                  1












                  1








                  1







                  In TikZ always the default unit for length values is pt. And we have




                  /tikz/xshift=<dimension>




                  So the default unit for xshift is pt.



                  In (1,0) you can think of cm as default unit but there is no default unit. Simply (1,0) is 1.x+0.y so it depends on the value of the x vector, which is initially set to (1cm,0).






                  share|improve this answer















                  In TikZ always the default unit for length values is pt. And we have




                  /tikz/xshift=<dimension>




                  So the default unit for xshift is pt.



                  In (1,0) you can think of cm as default unit but there is no default unit. Simply (1,0) is 1.x+0.y so it depends on the value of the x vector, which is initially set to (1cm,0).







                  share|improve this answer














                  share|improve this answer



                  share|improve this answer








                  edited 31 mins ago

























                  answered 41 mins ago









                  KpymKpym

                  15.8k23986




                  15.8k23986






























                      draft saved

                      draft discarded




















































                      Thanks for contributing an answer to TeX - LaTeX Stack Exchange!


                      • Please be sure to answer the question. Provide details and share your research!

                      But avoid …



                      • Asking for help, clarification, or responding to other answers.

                      • Making statements based on opinion; back them up with references or personal experience.


                      To learn more, see our tips on writing great answers.




                      draft saved


                      draft discarded














                      StackExchange.ready(
                      function () {
                      StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f469893%2fdifferent-dimensions-with-shift-and-xshift%23new-answer', 'question_page');
                      }
                      );

                      Post as a guest















                      Required, but never shown





















































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown

































                      Required, but never shown














                      Required, but never shown












                      Required, but never shown







                      Required, but never shown







                      -

                      Popular posts from this blog

                      What other Star Trek series did the main TNG cast show up in?

                      Image
                      .everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0; } 4 I'm referring to Picard, Riker, Data, Worf, Geordi, Dr. Crusher, Wesley Crusher, Chief O'Brien and family, Deanna Troi, Guinan. I know Picard and Worf show up on DS9, though I haven't seen it myself. I'm curious what happened to the characters after that last episode of TNG? star-trek star-trek-tng share | improve this question edited 10 hours ago Ham Sandwich 6,051 2 25 75 ...
                      Read more

                      Berlina muro

                      Image
                      La berlina muro ĉe Bethaniendamm, 1986 La berlina muro aŭ simple la muro [1] , nomita ankaŭ "kontraŭfaŝisma remparo" en propaganda lingvo de la iama Germana Demokratia Respubliko, estis parto de la interngermana limo, kiu dividis de la 13-a de aŭgusto 1961 ĝis la 9-a de novembro 1989 okcidentan Berlinon de la orienta parto de la urbo kaj de la ĉirkaŭa tereno de la GDR. Ĝi estis unu el la plej famaj simboloj de la malvarma milito kaj de la disdivido de Germanio. Pli ol simpla muro, la berlina muro estis fakte tuta defendokonstruaĵo kun du muroj, ena malplena strio, rondirvojo, gardturoj kaj alarmsistemoj. Dum la provo transiri la severe garditan limon al okcidenta Berlino multaj homoj estis mortigitaj. La preciza nombro de viktimoj estas pridisputita kaj ne certa; la nombroj anoncataj varias inter 86 kaj 238 mortintoj. La malplifortiĝo de Sovetunio kaj la politiko de liberigo gvidita de Miĥail Gorbaĉov ebligis al la orientgermanoj faligi la 9-an de novembro 1989 l...
                      Read more

                      Berlina aerponto

                      Image
                      Flugkoridoroj dum la blokado de Berlino La Berlina aerponto estas la provizigo de okcidenta Berlino per aviadiloj fare de la aliancanoj inter la 23-a de junio 1948 kaj la 12-a de majo 1949 dum la blokado de Berlino fare de la sovetia armeo. Enhavo 1 Historio 1.1 La aerkoridoroj 1.2 Unuaj flugoj 1.3 Plibonigo de la aerponto 1.4 Fino de la aerponto 1.5 Rozinbombiloj 1.6 Bilanco 2 Flughavenoj 2.1 Berlino 2.2 Okcidenta Germanio 3 Aviadiloj de la berlina aerponto 4 15-a datreveno de la aerponto 5 Bibliografio 6 Referencoj 7 Eksteraj ligiloj Historio | General Lucius D. Clay, militguberniestro de la usona okupadzono Jam antaŭ la berlina aerponto estiĝis la malgranda aerponto . La estro de la sovetia militadministracio en Germanio, Vasili Daniloviĉ Sokolovski, ordonis la 1-an de aprilo 1948, kiel reago al la konferenco de Londono inter britoj, francoj kaj reprezentantoj de Benelukso pri aligo de Germa...
                      Read more