X

NV5 Geospatial Blog

Each month, NV5 Geospatial posts new blog content across a variety of categories. Browse our latest posts below to learn about important geospatial information or use the search bar to find a specific topic or author. Stay informed of the latest blog posts, events, and technologies by joining our email list!



New ENVI Agent, IDL Agent, and GeoAgent Quick Guides

New ENVI Agent, IDL Agent, and GeoAgent Quick Guides

6/9/2026

The recent release of ENVI® Agent, IDL® Agent, and GeoAgent™ revolutionize how users interact with geospatial software. These agentic AI applications act as partners to plan, simplify, and execute complex workflows. Knowing where to start can be challenging for new users. To this end, we developed three new quick guides to... Read More >

Introducing NISAR Data Support

Introducing NISAR Data Support

6/5/2026

The release of ENVI® SARscape 6.3 in April 2026 includes preliminary support for NASA-ISRO SAR (NISAR) data. The NISAR mission is a joint Earth-observing satellite project between NASA and the Indian Space Research Organization designed to monitor changes in the planet’s land and ice surfaces using advanced radar imaging. It... Read More >

Monitoring Illegal Mining in the Amazon: Turning Persistent Data Into Actionable Insight

Monitoring Illegal Mining in the Amazon: Turning Persistent Data Into Actionable Insight

5/28/2026

Illegal mining over decades has constituted one of the most persistent and complex socio-environmental problems in the Brazilian Amazon. In recent years, with the increasingly intensive use of mechanized extraction, the associated environmental impacts—such as deforestation, intense soil disturbance, river siltation, and mercury... Read More >

From Answers to Action: Why ENVI and IDL Agents Go Beyond General AI

From Answers to Action: Why ENVI and IDL Agents Go Beyond General AI

4/20/2026

As generative AI tools like Claude and Gemini continue to gain traction, many organizations are asking the same question: Can general purpose AI actually support real geospatial workflows, or does it stop at surface-level answers? That question was front and center in our recent webinar, Meet Your New Partners in Science: ENVI... Read More >

Mapping Earthquake Deformation in Taiwan With ENVI

Mapping Earthquake Deformation in Taiwan With ENVI

12/15/2025

Unlocking Critical Insights With ENVI® Tools Taiwan sits at the junction of major tectonic plates and regularly experiences powerful earthquakes. Understanding how the ground moves during these events is essential for disaster preparedness, public safety, and building community resilience. But traditional approaches like field... Read More >

1345678910Last
«June 2026»
SunMonTueWedThuFriSat
31123456
78910111213
14151617181920
21222324252627
2829301234
567891011
23793 Rate this article:
4.0

New to IDL 8.3: !DEBUG_PROCESS_EVENTS System Variable

Anonym

In IDL 8.3, you can use the !DEBUG_PROCESS_EVENTS system variable to control whether or not IDL generates widget events at breakpoints.  By default, this variable is set to 1 which causes IDL to send widget events even when IDL encounters a STOP statement or breakpoint from the workbench.  You can turn off these events by setting !DEBUG_PROCESS_EVENTS to 0.  This change was made in IDL 8.3 to allow users to interact with IDL 8 Graphics (aka New Graphics) while debugging their programs. For example, if you run the following program (test_process_events_default), you will be able to interact (rotate, zoom, etc) with the surface when IDL is halted at the STOP statement. 

pro test_process_events_default
  !debug_process_events=1 ;default setting
  a=findgen(100)
  ng_sur=surface(hanning(200,200))
  stop ;breakpoint
end

However, if you run the program below (test_process_events_zero), you will not be able to interact with the surface when IDL hits the breakpoint:

pro test_process_events_zero
  !debug_process_events=0
  a=findgen(100)
  ng_sur=surface(hanning(200,200))
  stop ;breakpoint

end

In previous versions of IDL, widget events were stopped when IDL encountered at breakpoints. In IDL 8.3 you may encounter unexpected widget events because the default behavior is different. One example of this type of situation is debugging an application with widget timer events.  For example, if you run the application shown below (break_timer_example) in IDL 8.2, execution will halt at the STOP call and no widget events will be generated.   If you run this code in IDL 8.3 with default settings (!DEBUG_PROCESS_EVENTS=1), timer events will continue to generate even at when IDL encounters the STOP call. 

pro break_timer_example_event, ev
    widget_control, ev.id,get_uvalue=uval
  print, 'timer fired'

  widget_control, ev.top,timer=2
  stop

end

pro break_timer_example
  base = widget_base(/column, uvalue='base')
  widget_control, base, /realize
  xmanager, 'break_timer_example', base, /no_block
 
widget_control, base, timer=2
end
 

I hope that this information will be helpful. Thanks for reading!

Please login or register to post comments.