Re: When closed, does a substack whose destroyStack is true remains in memory ?
Le Monday, 27 Mar 2006, à 20:07 Europe/Paris, J. Landman Gay a écrit : Martin Blackman wrote: Thanks Andre thats what I was suspecting if following the docs to the letter. It doesn't seem like it should be necessary to save a file to disc though just to print out ! For the printing which I have done, mostly unstyled text, I haven't found any difference whether formatforprinting is on or off anyway. With some fonts, the difference in sizing is so minimal that the output appears the same whether formatForPrinting is set or not. But with other fonts, there can be a dramatic difference. On Windows machines, it is usually a good idea to set formatForPrinting to true. One way to get around the save-close-open restriction is to make a substack that will be used specifically for printing only, set its formatForPrinting to true, and save it with the mainstack. From then on, when you dump text into the substack's fields, they should use printer fonts rather than screen fonts. Thanks Jacque, but seems to me that I miss something : I had understood from the Doc that if the subStack has its formatForPrinting set to true, we must avoid to edit it (dump text in it) ? André Another way to deal with it, if you want to create printing stacks on the fly, is to set the formatForPrinting of the templateStack to true. Then when you create a new stack for printing, the property will already be set and will not require closing and reopening. This is how the Rev printing library does it. -- Jacqueline Landman Gay | [EMAIL PROTECTED] HyperActive Software | http://www.hyperactivesw.com ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution -- André Bisseret Directeur de recherche émérite Adresse : 140 rue E. Béthoux - 38220 Vizille Tél. : 04 76 68 15 24 Courriel : [EMAIL PROTECTED] et : [EMAIL PROTECTED] site Multifiches :http://www-clips.imag.fr/multicom/web_site_multicom/Multifiches/ site peinture : http://www.andre-bisseret.com/ ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: When closed, does a substack whose destroyStack is true remains in memory ?
André.Bisseret wrote: I had understood from the Doc that if the subStack has its formatForPrinting set to true, we must avoid to edit it (dump text in it) ? You will have to try it because I can't remember now. But I think putting text into a field is okay. What you can't do is edit text after it is already in a field. The IDE does something similar when it sets the formatForPrinting of the templateStack, so it should work. But test it. -- Jacqueline Landman Gay | [EMAIL PROTECTED] HyperActive Software | http://www.hyperactivesw.com ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: When closed, does a substack whose destroyStack is true remains in memory ?
Le Tuesday, 28 Mar 2006, à 19:23 Europe/Paris, J. Landman Gay a écrit : André.Bisseret wrote: I had understood from the Doc that if the subStack has its formatForPrinting set to true, we must avoid to edit it (dump text in it) ? You will have to try it because I can't remember now. But I think putting text into a field is okay. What you can't do is edit text after it is already in a field. The IDE does something similar when it sets the formatForPrinting of the templateStack, so it should work. But test it. OK, for me, this looks like a usefull precision ; I will test it (on PC of course :-) Thanks a lot André -- Jacqueline Landman Gay | [EMAIL PROTECTED] HyperActive Software | http://www.hyperactivesw.com ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: When closed, does a substack whose destroyStack is true remains in memory ?
The original thrust of this thread still puzzles me a little - how does one satisfy the requirement stated in the docs that a stack be closed and not in memory before setting 'formatforprinting' to true ? eg a typical application has a printing substack that gets cloned (thereby opening it) and filled with data before printing. I can set formatforprinting to true before cloning, but then the text fields will be edited before printing -which is also a no-no according to the docs, if I understand correctly. Martin Blackman ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: When closed, does a substack whose destroyStack is true remains in memory ?
Le Monday, 27 Mar 2006, à 14:09 Europe/Paris, Martin Blackman a écrit : The original thrust of this thread still puzzles me a little - how does one satisfy the requirement stated in the docs that a stack be closed and not in memory before setting 'formatforprinting' to true ? eg a typical application has a printing substack that gets cloned (thereby opening it) and filled with data before printing. I can set formatforprinting to true before cloning, but then the text fields will be edited before printing -which is also a no-no according to the docs, if I understand correctly. If I don't misunderstand your problem, you want to use formatForPrinting in the frame of a specific printing stack. Here is how I understood what is the necessary procedure : If you want to use the formatForPrinting property (setting it to true before printing), your printing stack must be a main stack, not a substack of your main stack. That's because, when your main stack is open, all its substacks are also in memory (even if they are not visible). If your printing stack is a main stack then, You can set its destroyStack property to true (purge stack on close in the Inspector, or in a handler, or in the msg box). After editing the fields of your printing stack, you saved and closed it (then it is removed from memory). At this time, it is possible to set its formatForPrinting to true (even while it is not open) and then print. After printing, set again its formatForPrinting to false. I recently tried this procedure, but without success I must say ! So I came back to the printing substack solution (hence, without formatForPrinting). I posted information on the solution I adopted in my last message in the thread Printing fields with images included by « set the imageSource of such char » (some insights). Hope that help Best regards from Grenoble André Martin Blackman ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: When closed, does a substack whose destroyStack is true remains in memory ?
Martin Blackman wrote: Thanks Andre thats what I was suspecting if following the docs to the letter. It doesn't seem like it should be necessary to save a file to disc though just to print out ! For the printing which I have done, mostly unstyled text, I haven't found any difference whether formatforprinting is on or off anyway. With some fonts, the difference in sizing is so minimal that the output appears the same whether formatForPrinting is set or not. But with other fonts, there can be a dramatic difference. On Windows machines, it is usually a good idea to set formatForPrinting to true. One way to get around the save-close-open restriction is to make a substack that will be used specifically for printing only, set its formatForPrinting to true, and save it with the mainstack. From then on, when you dump text into the substack's fields, they should use printer fonts rather than screen fonts. Another way to deal with it, if you want to create printing stacks on the fly, is to set the formatForPrinting of the templateStack to true. Then when you create a new stack for printing, the property will already be set and will not require closing and reopening. This is how the Rev printing library does it. -- Jacqueline Landman Gay | [EMAIL PROTECTED] HyperActive Software | http://www.hyperactivesw.com ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: When closed, does a substack whose destroyStack is true remains in memory ?
Thank you very much Ken for your answers ; I am taking them into account immediately :-) André Le Wednesday, 22 Mar 2006, à 23:42 Europe/Paris, Ken Ray a écrit : On 3/22/06 6:32 AM, André.Bisseret [EMAIL PROTECTED] wrote: Hi ! As far as a substack is concerned, from the Doc (on save, close, destroyStack…) I understand that : even if its destroyStack property is set to true, If I save and close this substack while the main stack remains opened, then this substack remains in memory. Yes, this is true - actually when you loaded the mainstack, all of its substacks get loaded into memory automatically and can't be purged until the mainstack itself is closed. P.S. : by the way, is it a means to check if a closed stack (or substack) is still in memory ? Well, as I mentioned above, closed substacks are still in memory if the mainstack is, so you could check for the mainstack in the windows or in the stacks to see if it is in memory. You can also use the mainstacks to get a list of stacks that are in memory. Ken Ray Sons of Thunder Software Web site: http://www.sonsothunder.com/ Email: [EMAIL PROTECTED] ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: When closed, does a substack whose destroyStack is true remains in memory ?
Ken Ray wrote: Well, as I mentioned above, closed substacks are still in memory if the mainstack is, so you could check for the mainstack in the windows or in the stacks to see if it is in memory. Maybe. The windows function is documented only to return a list of open stacks. The stacks function would seem to be the better one for testing if closed stacks are in memory, but it appears to behave anomalously and may not be reliable at this time. Try this: 1. Make a new mainstack named AAA; save it 2. Make a substack in that stack file named BBB; save it 3. Get the stacks RESULT: two entries for the filename to AAA are in the list, as we would expect. 4. Set the destroyStack of AAA to true 5. Close AAA 6. Get the stacks RESULT: the filename of AAA is in the list once, since BBB is still open; so far so good 7. Close BBB; because BBB has its destroyStack to false it should still be in memory, but - 8. get the stacks RESULT: the filename of AAA is not in the list :\ If the description for destroyStack is correct, BBB should still be in memory even if it's not open: If the destroyStack is false, closing a stack's window leaves it in memory. For the stacks function, the dictionary says: The list includes any open Revolution windows (such as the message box and menu bar). It also includes stacks that have been opened during the current session and then closed, unless the stack's destroyStack property is set to true. If I change the order so that the mainstack AAA has its destroyStack set to false and the substack BBB has its destroyStack set to true, I get the same result -- no entry in the stacks even though AAA is (according to the docs) still in memory. What am I missing? In my head this doesn't add up. -- Richard Gaskin Managing Editor, revJournal ___ Rev tips, tutorials and more: http://www.revJournal.com ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: When closed, does a substack whose destroyStack is true remains in memory ?
On 3/23/06 7:03 AM, Richard Gaskin [EMAIL PROTECTED] wrote: Ken Ray wrote: Well, as I mentioned above, closed substacks are still in memory if the mainstack is, so you could check for the mainstack in the windows or in the stacks to see if it is in memory. Maybe. The windows function is documented only to return a list of open stacks. The stacks function would seem to be the better one for testing if closed stacks are in memory, but it appears to behave anomalously and may not be reliable at this time. Try this: 1. Make a new mainstack named AAA; save it 2. Make a substack in that stack file named BBB; save it 3. Get the stacks RESULT: two entries for the filename to AAA are in the list, as we would expect. 4. Set the destroyStack of AAA to true 5. Close AAA 6. Get the stacks RESULT: the filename of AAA is in the list once, since BBB is still open; so far so good Wow... really? I would have thought that BBB would close to since its mainstack closed. But whaddya know! :-) What am I missing? In my head this doesn't add up. What does the mainstacks say? I've found that this seems to truly show what's in memory (or at least, the mainstacks that are in memory)... Ken Ray Sons of Thunder Software Web site: http://www.sonsothunder.com/ Email: [EMAIL PROTECTED] ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
When closed, does a substack whose destroyStack is true remains in memory ?
Hi ! As far as a substack is concerned, from the Doc (on save, close, destroyStack…) I understand that : even if its destroyStack property is set to true, If I save and close this substack while the main stack remains opened, then this substack remains in memory. If this is true, then I understand that it is not judicious to set « formatForPrinting » to true for this substack. So, for a specific « printing stack » I have to use a second main stack, instead of a substack. Am I right ? Thanks a lot in advance for validating (or invalidating) these claims. P.S. : by the way, is it a means to check if a closed stack (or substack) is still in memory ? Best regards from Grenoble André ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
Re: When closed, does a substack whose destroyStack is true remains in memory ?
On 3/22/06 6:32 AM, André.Bisseret [EMAIL PROTECTED] wrote: Hi ! As far as a substack is concerned, from the Doc (on save, close, destroyStack) I understand that : even if its destroyStack property is set to true, If I save and close this substack while the main stack remains opened, then this substack remains in memory. Yes, this is true - actually when you loaded the mainstack, all of its substacks get loaded into memory automatically and can't be purged until the mainstack itself is closed. P.S. : by the way, is it a means to check if a closed stack (or substack) is still in memory ? Well, as I mentioned above, closed substacks are still in memory if the mainstack is, so you could check for the mainstack in the windows or in the stacks to see if it is in memory. You can also use the mainstacks to get a list of stacks that are in memory. Ken Ray Sons of Thunder Software Web site: http://www.sonsothunder.com/ Email: [EMAIL PROTECTED] ___ use-revolution mailing list use-revolution@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
