ruby-****@sourc*****
ruby-****@sourc*****
2013年 4月 2日 (火) 18:19:34 JST
-------------------------
REMOTE_ADDR = 70.49.48.128
REMOTE_HOST =
URL = http://ruby-gnome2.sourceforge.jp/hiki.cgi?tut-gtk2-dancr-rbcatut-dwc
-------------------------
@@ -91,7 +91,7 @@
(12.3.2.1.A1){{br}}
Nevertheless, for those of you, who in the absence of the above 'translate(tx, ty)' method, do not mind some extra programming work, I decided to provide the following, a bit silly program, that reveals all the hidden issues, not seen from the example above.
- You do not have to waste your time, reading this example, all you really need is to carefully study all the three images shown in this section (12.3.2.1), and try to figure out what the differences mean, and possibly, what caused them. Here are some hints: the majority of problems are related to the size of the drawing surface, as well as scale, which are only completely revealed if the drawing is not done right next to the edges of the drawing surface.
+ You do not have to waste your time, reading the following example (I suggest you run it, though, just to gain confidence in the code.) Instead of reading the code below, you can only carefully study all the three images shown in this section (12.3.2.1), and try to figure out what the differences mean, and possibly, what caused them. Here are some hints: the majority of problems are related to the size of the drawing surface, as well as scale, which are only completely revealed if the drawing is not done right next to the edges of the drawing surface.
We will revisit this program again in the above mentioned section 12.3.4, where we will see a better and more efficient way to handle displacements in cairo code. By then you should also have a much better understanding of 'canvas' (drawing surface) size and scale related issues, which are there finally addressed in full extent.