RTI: Timeline for fixing PrintSetup for OI32 and OIPI32 (OpenInsight 32-Bit)
At 16 OCT 2002 12:25:24PM Ray Chan wrote:
We're calling the PrintSetup function from within our MDI to set the default printer. This is useful from time to time.
At present, if you change the default printer, you must exit out of the MDI frame and come back in before it takes. OIPI32 doesn't pick up the new default printer right away.
Will this be fixed any time soon? We could do a Stop/Start32 to simulate exiting and returning to the MDI frame which I think would work. But before we implement this clutzy code which we prefer not to, does RTI plan on fixing this soon?
Thanks a bunch,
Ray Chan
At 21 MAR 2003 07:15AM Bertil Strom wrote:
Hi,
Changing default printer from within a MDI window.
It's told to be fixed but I can't get it to work.
Are there any parameters involved with the call to the utility
I use the default printer seems to change
but still the output is to the old default printer.
Any idea of
At 21 MAR 2003 09:27AM Bob Orsini (Revelation Software) wrote:
If you get the currentdevice using the get_printer command and in the init command of OIPI use that as your printer you will be using the current default printer.
At 04 APR 2013 09:21AM Tony Lillyman wrote:
Hi Guys
Just got back on the forum after 3 years away.
Have been reacquainting myself with OI and had this issue with Get_Printer Hanging
After a 3 HOUR search and much cursing I found the v9.1 upgrade note that advised between selecting the OIPI Version and selected VSPRINTER instead of VSPRINTER2 and everything works great.
Strange how such a note didn't come up on the Forum search.
Obviously RTFM applied not to me.
Onward …
Tony
F1 Data System
Sydney Australia