View RSS Feed

Development Team Blog

  1. Diagnosing Studio and compile time performance problems

    by , 22-Mar-2010 at 08:00 AM (Development Team Blog)
    When it comes to performance working in the Studio as a developer, as opposed to running the application, there are generally two performance critical areas. The first one is the Studio Parser, which is the foundation for CodeSense, Visual Modeling, Go-To-Definition and more. The second performance critical area is when compiling. Unnecessarily long and slow compile times can make for a very frustrating experience working with the Visual DataFlex Studio.

    Sometimes you may not even ...

    Updated 17-Mar-2010 at 05:25 PM by Sonny Falk

    Attached Thumbnails Attached Thumbnails Click image for larger version. 

Name:	comp-perf.jpg 
Views:	1878 
Size:	26.8 KB 
ID:	3799   Click image for larger version. 

Name:	parse-perf.jpg 
Views:	1827 
Size:	29.0 KB 
ID:	3800   Click image for larger version. 

Name:	studio-load.jpg 
Views:	1828 
Size:	29.8 KB 
ID:	3801   Click image for larger version. 

Name:	studio-parse.jpg 
Views:	1900 
Size:	51.5 KB 
ID:	3802   Click image for larger version. 

Name:	bigws2.jpg 
Views:	1855 
Size:	50.7 KB 
ID:	3803   Click image for larger version. 

Name:	bigws1.jpg 
Views:	1886 
Size:	23.6 KB 
ID:	3804  
  2. Suggestions - How we make mountains out of molehills

    by , 21-Sep-2009 at 08:00 AM (Development Team Blog)
    There was a recent [URL=""]forum thread[/URL] suggesting that the Studio's codesense should provide assistance with index selection for the Find command. We noted that this suggestion actually was implemented but that it was implemented in a slightly different manner. As expected a lively discussion ensued. This presents a good opportunity to discuss how we implement suggestions. We can use this suggestion as an ...
  3. CodeSense Improvements

    by , 27-Jul-2009 at 01:44 PM (Development Team Blog)
    [I]Note: This information applies to Visual DataFlex 2008 and higher[/I]

    During development of 12.0 and 12.1 we received feedback with several suggestions for improving CodeSense. Many of those suggestions, along with some other ideas we had during development, were out of scope for 12.0, so we logged them in our bugtracker database as either bugs/suggestions. During development of 12.1 we fixed a lot of the pure bugs and performance issues, but we didn't have time to address some ...