Quentin Mathé wrote: > I understand. But doesn't that contradict with using DPSgsave and > DPSgrestore? So shouldn't we replace these functions when they are used > by NSGraphicsContext equivalent methods? Or are they too slow to be used > all the time? > May be I didn't truly understand what you mean in a previous mail though. >
Sorry for being a bit unclear in my previous mail. There is of course a replacement for DPSgsave and DPSgrestore. Simple enough these are the instance methods saveGraphicsState and restoreGraphicsState on NSGraphicsContext. In the example you had copied over from Apple the class methods with the same name where used and I explained the difference between these and DPSgsave/DPSgrestore. I really should have pointed to the instance methods as well, which should be used instead of the functions. This is what happens when you are to lazy to explain something in a mail, you then have to write a second one. But it is really important to get this point over, there isn't much reason to use the PS/DPS functions in applications code and sometimes it may even be faster to use the high level code, as this allows GNUstep to do more optimization in between. It still is a bit different within GNUstep gui, but even there I try to use more and more high level code. _______________________________________________ Etoile-discuss mailing list [email protected] https://mail.gna.org/listinfo/etoile-discuss
