CVI 2009SP1 release

Similar Questions

• Why CVI have functions that duplicate the functions of ANSI C file handling (ex: Openfile)?

  Why CVI have of file manipulation functions that seem to reproduce the functionality of the ANSI C functions?

  Is there an advantage to using the CVI functions?

  As the CVI was released (1987), until the ANSI-C standard is released (1989) maybe the question should be the other way around!

  In those early days, CVI was supposed to be cross-platform, so it was logical to develop a set of libraries that operate in the same way across the different computers it was targeted at. These days, the focus seems to be primarily under Windows, so this philosophy at the beginning is a bit redundant, especially, as you say, with the widespread adoption of ANSI-C.

  Personally, if there are similar functions in CVI, and ANSI, I'll go for the ANSI, whenever for portability of the reasons, but yet I write code in a number of different programming environments.

  JR

• Unusual tab background color

  Hi all

  I always thought that a tab control on a Panel set to use Windows Visual Style for controls can have two background color of tab pages:

  • Some shade of light gray / white when tabs appear on the top of the control
  
  
  • The Panel background color if the tabs are on the other sides of the contrl

  I found, however, a tab control that behaves differently, always showing the white background regardless of the position of the tabs: table below compares the control tab on the left, behaving 'normally', with the one on the right which is white. Consider color background of the pages tab cannot be defined in the IUR editor since the control follows the theme of Windows (this remains true for both controls).

  

  Now, I don't know how I got this 

  Does anyone have an idea on how to do it?

  I enclose the above sample Panel to allow you to test.

  I found it initially on CVI 2009SP1 on Win7 with CVI2012SP1 TIME machine, but the control displays the same beaviour on CVI2012SP1 too.

  Roberto,

  Maybe I misunderstood, as I CVI2013 and therefore cannot make a direct comparison, but I was able to get the same color... Have you tried to deselect 'Use Windows Visual Style for controls', change the color and then re - activate the checkbox? That worked for me...

• Problem with the identifier to browse

  Hello

  one of my projects is composed of many files. If I open it or modify the mode of construction, it takes time to generate navigation information.

  Now, if I use the identifier to see where a function is called, it tells me that this function is not called directly.

  This information is wrong, it is only due to the fact that consultation information do not yet exist. Little more wait time will result in a correct result.

  I suggest to solve this, for example, by showing a hint in the identifier to browse (like 'browse information not yet available, please wait or take a coffee... »)

  Hi Wolfgang!

  We wanted that the generation of information navigation to be less intrusive as possible. That means, that it shouldn't block components in the user interface or cause distractions through notifications that the ADE generates semantic information in the background permanently. In addition, waiting for longer periods is currently the case for relatively larger projects. To the navigation information is generated completely, all the available semantic information is considered to be incomplete.

  Referring to the lack of maturity of the CVI 2013 release, we realize that there is room for improvement. Focusing particularly on the navigation information, we take suggested improvements into account for future updates and versions of the product. It's caching of navigation information and improve the browsing experience when you use the functionality of the user interface for browsing source code.

  Thank you!

  -Johannes

• RegReadString with 64-bit operating system

  Hello

  Usually, I use the RegReadString/RegWriteString feature for read and write on Windows Reg system.

  It works without problems on Windows Vista and Windows7 32 bit, but under WIndows7 64 Bit does not work.

  Example:

  #define WIN_KEY "SOFTWARE\\Microsoft\\Windows NT\\CurrentVersion"
  iRtrn = RegReadString (REGKEY_HKLM, WIN_KEY, "ProductId", szBuffer, 256, &lSize);)

  This example returns normally windows Product ID, but under Win7-64, I got error "registry values is not exist"(-5068). "»

  RegWriteString does not work too...

  Can you help me?

  Thank you

  Daniele

  Hello Daniele,

  An important thing to realize when running a 32-bit on windows 64-bit executable, it's that all registration applications will be redirected by the Wow6432Node.  For some reason, Microsoft chose not to place the product identification information in the redirected location (HKLM\SOFTWARE\Wow6432Node\Microsoft\Windows NT\CurrentVersion).  Only 64-bit applications are capable of reading from the non Wow6432Node location, where the ID of the product.

  Generally, the type of information you're looking for is better recovered through a certain type of script such as VBScript and WMI .  Until the CVI 2009 releases (giving you the ability to create native 64-bit applications) you can retrieve this information in the registry with an application of CVI.

  NickB

  National Instruments

• scrool mouse wheel events

  Hello!

  I noticed that in CVI 9.0 when using a control slide (hot mode) with the wheel of the mouse, the only event generated is EVENT_MOUSE_WHEEL_SCROLL.

  But in 2013 CVI the same control generates EVENT_MOUSE_WHEEL_SCROLL, EVENT_VAL_CHANGED, and EVENT_COMMIT.

  This behavior is correct?

  Thanks in advance.

  The reason why these events are sent 2013 CVI is because the operation mouse wheel really does not change the value of the control under CVI 2013, which happened not to 9.0. This has been implemented from a deposit of idea exchange and it has been documented in the CVI 2013 release notes (search for "mouse wheel").

  The events are not referenced explicitly in the release notes because the essential difference is the value of the control changes. Once that happens, then, as Wolfgang mentioned, events must be sent.

  Luis

• Print texts in different formats on a single page

  Hi all

  Is it possible to print on one page text in different fonts and sizes? It seems that PrintTextBuffer prints all text on a single page at a time and there is no chance to change the format. Thank you

  LT

  I must confess that I give you this suggestion, but I did not use these functions for several years ; test your function on my system now (CVI 2009SP1 on Win7 with HP LaserJet printer) I have the same results as you.

  Due to the limitations of this method of printing, I moved quickly to the other printing modes: there are many discussions you will find in the forums on the reports, but basically, you can:

  • Create a hidden Panel 'report' where to print your data on the standard controls (strings, numbers, graphs, tables and so on) and use PrintPanel to print it
  • Use NIReports instrument
  • Use Office report print (via Word or Excel)
  • Create a PDF file
  • ... (other methods that I can't think of right now)

  One is probably the fastest: you already used to create panels and after a short trial, you can set the correct control/panel aspect for a good report. It also allows you a limited preview if you want to.

• How to force the compilation released executable before running the distribution of LabWindows/CVI kit?

  I am new in 2015 of the CVI. I used CVI 7 and when I chose "Create the Kit of Distribution", when I was still in debug mode, Labwindows asked me to build the executable of setting before creating the Distribution Kit. This does not happen to CVI2015, and the Distribution Kit is created with the latest built executable version, although I made a few changes in my code! This is a problem since I work in debug mode and I usually forget to build the executable of liberation before calling the distribution kit, so I need CVI to do it automatically like CVI 7 did. I suppose that there is an option to do this, but I can't find. Can someone tell me please how to resolve this problem and force CVI to build the exe version before building the distribution kit? Thank you.

  Today, I've solved quite simply create a new distribution. The previous like unsing was automatically imported by CVI7 project. By creating a new distribution, now when I change something, CVI ask me if I want to build the release. So I did not understand the problem but I solved it by editing a new distribution kit.

• CVI executable causes an on update of Windows 10 anniversary 0xC0000005 Access Violation.

  Created executables always causes an Access Violation (0xc0000005 exception) to the closing period on Windows 10 RS1 (update of the anniversary).

  This problem occurs in LabWindows CVI 2015 and 2015 SP1.

  How to reproduce: simple program to create and compile with the (x 86) release profile by default.

  for example:

  #include "test.h".
  
  
  
  
  int ph;
  int __stdcall WinMain (HINSTANCE hInstance, HINSTANCE hPrevInstance,
  
  					   LPSTR lpszCmdLine, int nCmdShow)
  
  {
  
  	If (InitCVIRTE (hInstance, 0, 0) == 0)
  
  		Returns - 1;    / * memory * /.
  pH = LoadPanel (0, "test.uir", group of EXPERTS);
  
  	DisplayPanel (ph);
  
  	RunUserInterface();
  return 0;
  
  }
  int CVICALLBACK CallExit (int, int int event, control panel,
  
  						  void * callbackData, int eventData1, int eventData2)
  
  {
  
  	switch (event)
  
  	{
  
  		case EVENT_COMMIT:
  
  			QuitUserInterface (0);
  
  		break;
  
  	}
  
  	return 0;
  
  }

  The problem is visible on the control panel > reliability history > Error Reporting:

  

  Also the code of the executable file (exit code) is always 0xc0000005 instead of zero.

  To check out more easily code can be called the executable through file .bat:

  off @echo
  
  Test.exe
  
  echo ExitCode = %ERRORLEVEL%
  
  pause

  I have observed that if multiple instances of the same program are running, only block when the last instance is closed. It seems that the problem occurs at the time that the CVI runtime is released from the ram. (The latter is only a guess)

  Hello

  We did some research and saw that the failure is related to some police files in

  c:\Windows\SysWOW64\cvirte\fonts

  c:\Windows\System32\cvirte\fonts

  Could you try deleting these files and see if the heater is always performed. If this isn't the case, it would be a work around if you do not use these fonts.

  We continue the investigation to see the exact cause

• Real-time execution trace toolkit to optimize the Labwindows/CVI code

  Hello

  I am trying to optimize a code in real-time in LabWindows/CVI by minimizing the time of each section of the code is taking and find bottlenecks in the code. I check this time using the real-time execution trace toolkit.

  However, I just found it seems to be a constant error when you use the tool of real-time execution trace.

  When I put the traceviewer 'start' and 'stop' right after the other, I get around shift schedule 9us. It seems that the CPU will in some "idle" after the start of the trace mode, or maybe it's the time of communication or something.

  I'd appreciate it if someone could give me an idea of why this is happening. The time of real-time application window is very limited and I'm trying to minimize the time as much as possible. Even the United States 9 error is difficult to resell.

  I used the following code:

  TraceConfigure (1, 1, 0, 25000, NULL);
  
  TraceStart ();
  
  TraceStopAndSend (HOST_ADDRESS);

  and there is a photo in the toolkit of real-time execution trace.

  Thank you.

  Generally, you might be better off picking off the clock at the beginning and end of what you want to track. RTETT my introduce overhead that becomes difficult to quantify... Which is what you probably already see. The debug mode will also implement a ton of overhead. Then... Destemming of the clock in release mode will probably give you you the best estimate.

• CVI 2015 & Windows SDK

  Installation of CVI 2015 on laptops Win7 enterprise.

  Work project recently installed, registered, launched, went to its construction, and ICB 2015 requires the installation of the Windows SDK 8.1.  Obtained after popup error message.

  

  I've traveled on ni.com/frinfo, entered the code and was immediately sent to the Microsoft SDK 8.1 page.  No information OR on what to do, how to install, how to bind the SDK of the CVI.  Tried to download the SDK 8.1, and he repeats to me that the file is corrupted.  I tried SDK 10.0, which says that it supports Win7, downloaded, installed, ICB does not recognize anything, wants 8.1 SDK.

  I'm dead in the water.  Help!

  Problem solved, sort of, by devious means, a way more harmful to complete the installation:

  Find and run the file from the DVD: D:\Distributions\CVI\Products\MSDTRedistributables_WindowsSDK_81\sdk\sdksetup.exe

  This creates successfully the folder C:\Program Files (x 86) \Windows Kits\.

  I have no idea why the installed does not automatically to my Windows 7 laptop.  I hope that NEITHER solves this problem by releasing CVI2015 SP1.

• Bug CVI research dialogue...

  I, again, don't find not the bug overview page. so, I'll post here:

  using CVI 8.5, during a search (CTRL + F). by selecting the check box "Multiple files" but NOT the checkbox "search folders", if the specified directory in the "search in files" options is not valid, the search will complain and not run. Note that this specific option is disabled since "Find in files" is unchecked, then the search does not have to worry about what's written there...

  (also: is there a page to track bugs submitted to OR?)

  You're right, it is a bug. I entered a bug for her report (#130204).

  As far as I know is not a publicly available database that you can use to check the status of a bug report. Each version of the CVI includes a list of all bugs that have been resolved for this release in its readme file, and you can also see this list online (for example, here is the list for the 8.5.1 release). If a fix is not yet released publicly, I recommend that you post a question here or send a mail DIRECTLY, ask questions about the status of the bug report.

  Luis

• new features of CVI 9.0

  is it possible to have a list of all the novelties of the CVI 9.0 (especially the features of C99) without having to watch a webcast?

  I'm sure I'm not the only one who can not watch a webcast to work, also broadcasting on the Web is not subtitled and I do not have his work. Finally, and above all, many users of this forum is not the native English speakers and will not understand anything of this speech.

  Thank you very much.

  Hello

  Have you seen Release Notes found here?  The information you are looking for must be there.  Please let me know if I can clarify or add to anything in this document.

  Thank you!

  NickB

  National Instruments

• Crash of CVI 2013 with the debug version

  Hello

  I'm trying to migrate a large enough project of CVI 2012SP1-CVI 2013 and feels the clang compiler crash when I try a debug on some files.  Clang will also plant (' Labwindows/CVI the Clang compiler has stopped working... ") so I am just trying to compile the file (ctrl-k) in the editor.  Here's what I found:

  • A release not crushed
  
  
  • By turning the C99 power button has no effect
  
  
  • Change the warning level has no effect (other than the types of warnings that I get, of course)
  
  
  • Change the ' debug ' on 'No run-time check' eliminates the crash.
  
  
  • 'Enable. Option of obj"eliminates the crash.
  
  
  • By turning precompiled headers power has the effect.

  Here is the long message I get from the compiler when this happens (including all the warnings that are always displayed when the level is set to 'None'):

  

  Any thoughts?  Unfortunately it's a pretty big project that I can't post and it doesn't seem to be an indication of the or the lines in the file that he has problems with it, so I can't limit, although it seems to hint that he has problems with the structures of some sort.  The PC is running Windows 7 Pro 32 bit if it matters.

  Thank you.

  Hi tstanley,

  We could find the cause of the accident of the compiler from your code. We will settle in the next update and you can follow with bug ID 422577.

  The issue occurs when in a function, you have a call to a function that returns a structure in a global variable and then refer to this world in another function. For example:

  struct Foo foo; global variable foo
  
  Sub FuncA()
  {
  
  foo = GetStructFoo();
  
  }
  Sub FuncB()
  {
  
  do something with foo / / crash
  
  }

  In this case is because we are bad associate information of temporary pointer with foo in FuncA. Then in FuncB, clang will crash when it tries to access this pointer information.

  There are two workaround solutions, but both require changes in the code.

  1. modify the function that returns the structure, GetStructFoo in my example, the return via a pointer parameter:

  void GetStructFoo(Foo *foo);

  2 use a temporary local variable to manipulate the structure returned and then assign its value to the overall structure:

  struct Foo tempFoo;

  tempFoo = GetStructFoo();

  foo = tempFoo;

  In our next update, we will include the fix for this bug.

• CVI - Windows 10-2015 and beyond

  I'm looking to revive my support CVI and the CVI 2009 update to the current.

  In order to justify the leap, I would like to learn more about plans for CVI2015:

  • Support for Windows 10 (office only, but for the development platform and for the target platform)
  
  
  • Distribution packaging formats (for "Hello world")

  History / context:

  • Microsoft seems to be ready to everyone they can grow to 10 Windows. With a cycle of publication of two years for the CVI, my fear is that Win 10 ICB support can come in Q3 2017. (Note that Windows 8 found were from Sept 2011 and RTM was August 1, 2012. CVI necessary accompaniment, the next version: CVI 2013 was released in August 2013. Where my 'next release' forecast of 2017.)
  
  
  • Distribution packages are passed from 5 to 12 25-75 MB in the last several releases. The minimum size for 2013 CVI is a deal breaker for us - I get complaints about 25 MB.

  I don't want to be too negative - ICB done great things for us, but these two complex (and difficult to master!) questions are really two points pain I want to see progress.

  Thank you

  Ian

  Ian,

  Regarding your question Windows 10, we conducted tests with versions of Windows 10 and we do not expect our products to work with this operating system. However, we cannot claim official support until our products have been tested with the official version of Windows 10.

  Regarding your concern about size of deployment, we mentioned this feature incompatibility in our readme CVI 2013 for the clients of this KB: http://digital.ni.com/public.nsf/websearch/A402AA9C304A33E186257B8E00630D00?OpenDocument

  The KB is not entirely explain why we have chosen to make this decision but makes us think of this feature a good amount and in the end we had to make compromises. The key points we considered where:

  • It is much more difficult to scale the installation programs using merge modules, as compared to the msi files
  
  
  • MSI files using allows NO place easier fixes to customers
  
  
  • It's easier to implement additional deployment capabilities on top of MSI than the merge modules

  I hope this helps.