Strange command-line printing behavior
s.r.chinn
•print Gwidth
2int Gwidth
•printf "%g\r", Gwidth
2intf "%/g\r", Gwidth
2int Gwidth
•printf "%g\r", Gwidth
2intf "%/g\r", Gwidth
What is also odd, is that when I copied and pasted the History lines into the above extract, it appeared correct. I edited it to show what my PC monitor displays. It appears that the monitor output result is the echoed print command, over-written by the variable value. Has anyone else encountered this?
I added a workaround which requires a nightly build from 2011-08-02 or later. Here is the description of the change:
I've attached a zipped Igor procedure file which disables the use of BitBlt (Windows) or ScrollRect (Macintosh). Place this file in the Igor Procedures folder in your "Igor Pro User Files" folder. To find your your "Igor Pro User Files" folder, choose Help->Show Igor Pro User Files. Once you have done that, Igor will automatically load the file and execute the IgorStartOrNewHook function at launch time. This will set ScrollingMode to 1.
REMINDER: This feature is not in IP 6.22A. It requires a nightly build from 2011-08-02 or later.
May 10, 2012 at 08:15 am - Permalink
I tried this and it does not solve the print scrolling problem. As I mentioned in a follow-up post to the mailing list, the scrolled results disappear after an IP window refresh, but then re-occur. This is still happening.
Is there any way to monitor from Igor the status of the scrolling mode?
Steve
May 10, 2012 at 08:45 am - Permalink
I will look into alternate drivers for the Dell monitor.
May 10, 2012 at 08:56 am - Permalink
I'm not sure precisely what you mean by "this". Test it by manually executing:
Then do your Print test. This "should" solve the problem.
Yes:
If you have a Dell-specific driver then it could be the culprit. Otherwise try updating the driver for your video output card or circuitry rather than the monitor. Also look in the Display control panel for any or driver-specific video settings (e.g., acceleration). Try turning them off.
May 10, 2012 at 11:29 am - Permalink
I installed a IP6.23 nightly build (10 May 2012) along with Set Scrolling Mode To 1.ipf, and I no longer get the over-writing artifact in the History from command-line print statements. In case other IP users new to Windows 7 encounter this problem, this solution may help you too.
The exact cause of the problem is still puzzling, and its occurrence depended on several factors too complicated to describe fully here. The bottom line is that WaveMetrics came through again.
May 15, 2012 at 03:04 pm - Permalink