LabVIEW 2015 scrollbar bug on block diagram

Similar Questions

• LabVIEW move things on different computers block diagram

  We have a site here license to my work, and I use several computers to develop and deploy our test code. However, I discovered that between computers, often things move on the block diagram simply by opening them on different computers. Mainly text fields. We have some text fields next to rows of a table of block diagram that are alliged with the lines of table on a single computer, while the same without code change when opened on another PC, all text fields are compressed vertically so that they no longer align with the rows of the table. This could be the cause, and is it possible to fix it?

  Thanks for the replies. It is the size of the police which was the issue. However, although I have tried to change the default Application font size (by the "default font" settings of "modification of the characteristics of text") to match the computers that had "correctly" it was not solved the problem. I finally realized that I had to change the police system from the Options > environment > fonts > menu fonts application of the front screen of "Open/create", then completely restart LabVIEW. Problem solved.

• How to display the drop-down list box in MS excel by using labview report generation toolkit? pleasepost code block diagram?

  How to display the drop-down list box in MS excel by using labview report generation toolkit? Please post the block diagram of the code so that I can able to generate from the drop-down list box in excel with the menu drop-down...

  Like this. (edition, use the reference forms instead of the reference to the worksheet)

  Ben64

  

• Bug: Façade objects relative position changes when you move the fusion VI on block diagram

  I posted a bug report on the LAVA, here:

  http://forums.lavag.org/front-panel-objects-relative-position-change-when-placing-merge-VI-onto-bloc...

  If someone at home OR can reproduce, can I please get a CAR #?

  Thank you

  -Jim

  Hi Jim,.

  This was reported to R & D (# 139212) for further investigations.  I don't know if it's more embarrassing fall into the range of functions and reorganize the façade or drop out of the front and hope that the code of the Subvi is not disseminated in the block diagram.  Because the code (or orders) are selected after a fall, and you can switch between diagram and panel above all keeping this selection, at least you can move the code as a whole, right?

• LabVIEW: Null window... stopped to stranger on the block diagram

  Hello

  I have a pretty important program that has been written in Labview 6.0. Recently, we have upgraded to Labview 9.0 and this program has been exported to an executable file with the new version.

  When you run the executable file, I sometimes have the following error as seemingly random places. I was not able to crash when not to use the executable file. LabVIEW: Window zero. The first level VI ".vi" stopped to stranger on the block diagram of ".vi".

  

  I apologize for having empty on the names of vi, but I can't give names of vi, say what is the software or code. I can tell it uses NI USB-6212 IO cards, interfaces with the instruments of Rhode and Swartz and uses a lot of file i/o.

  I was hoping someone could give me a hint on how to debug such a mistake. I noticed that when this error occurs, the memory usage almost doubles.

  Thank you

  James

  
  

• LabVIEW 2015 Buffer Allocation Bug?

  This happens in LabVIEW 2015 SP1 32 bit running on 64 bit, Win 7; It does not appear to occur in 2014 of LabVIEW.

  Look at the screenshot, the Subvi is a simple in and out with no operation.

  

  In the preliminary examination International one copy buffer product (red circle), but not in other cases. Does anyone have an idea why this is the case? I would like to use the structure of the International preliminary examination to select a subset of data to operate on, so the other case does not apply.

  The screws are attached in the zip file.

  See you soon,.

  McDuff

  If you inline the Subvi, allowance disappears.

• Copy and paste between versions of labview block diagram

  I try to reuse code from labview labview 2015 2013 (because I need this code with a 13 rio compatible).

  So I just tried to copy and paste items hitherho comics.

  He ended that the elements of the comic have been pasted as a bitmap instead of the original objects.

  Do I have to use a few different copy / paste possibility that strg-c and Ctrl-v or do I have to register each sub - vi in 2013, which would be

  do useless?

  You can't copy + paste between versions of LabVIEW.

  You will need to save for the previous version and open in the LabVIEW version that you want to paste to.

• LabVIEW block diagram icons became invisible

  I'm a bit of a loss here.

  I worked on a fairly large vi of higher level for a while when suddenly several vi system developed display problems.  In particular, all the screws of the FPGA module no longer appear on the block diagram.  They are there, because I can move the properties and thread them, but they are invisible.  Even if I add a new menu, it is invisible.  Is the same for the control on the structure of timed loop block.  The loop is visible, but the controls are not.

  I have attached a picture of a part of the vi that shows what should be a 'open FPGA reference' and a timed loop.  As you can see, the wires are connected and it compiles and works very well, but there is nothing on the screen

  It is specific to this vi.  If I create a new vi and add the same vi they look very well.  As far as I know, I did not change to any display settings.

  Any suggestions?

  Hi Nathan,

  You should be able to get a global position by moving one of the scroll bars.  When you click or drag the scroll bar a small box should appear (right of the cleaning if the BD is enlarged or below the bar of horizontal scrolling if the BD is is not maximized) giving the global coordinates.  If you find that you are outside about 15000 pixels (I don't know if it is a hard cut) are trying to move close to the origin.

  You should not recreate anything.  Actuall you can find the line where the icons become visible.  In a quick test here he looked about 15000 pixels.

  

• Reduce clutter in the control on my block diagram reference...

  Is it possible to reduce the amount of clutter on my block diagram when needing to enable and disable controls so that the tests are running? I know that I can place the instruction box in a Subvi, but I'm looking for the best method recommended to reduce clutter when listing references. Using LabVIEW 2015.

  Here is a small example of what I speak, there will be only for references to be added as the devlops of VI.

  

  Thank you

  Kellen

  rkmadse wrote:

  When you say I can clustor FP, say things that I did, and I have a group of controls such as those below in a clustor. I still have to generate reference constants, which are then placed in clustors. If I want to disable I would have then to consolidate each reference in the clustor, then ungroup and disable each control individually. I bet I'm really missing the point here and I'd love more explanation.

  Thank you

  Kellen

  My main problem is not being able to place real dangerous in a Clustor.

  You think about transportation, when I talk about the horse. Your façade elements can be in a cluster, and then you can use the reference to the pole to disable all. See:

  

  You will get a façade looking slightly different between the two options if you use disabled and Grayed out because when you grey on the whole cluster, the gray edges. When you gray unique items in the cluster, the cluster edges remain normal.

• Clean using SubVIs block diagram

  Hi guys and welcome to my first post!

  I m a bit new to labview, so be a little patient, if I do not understand everything immediately

  Im working on an existing program that is used to control an MCU on BabyLin on my front, although I have a visualization to see live changes to the system. The program works very well so far, but I m trying to clean up the block diagram. This should be done by subvis, right? I ve read a lot about the size of the block diagram should not increase my screen. Well, im at a length of about 3 x 2 screens (24 "!) after trying to use subvis and to shorten the distances between structures. The only things remaining are huge amounts of local variables and references (they existed already before I got to know the program), mainly for viewing. If I create a Subvi part containing the people of the country, it will change the references that does not make the program more readable (and small), and I guess I can't put a new Subvi on references + Subvi.

  You have any ideas what to do? I hope that I forgot something, otherwise, do not hesitate to ask.

  Kind regards

  Leo

  Bob_Schor wrote:

  To get a handle on the structure of your high-level code, write down (as if you were telling your boss or tell your wife - who knows, they might be the same person!) that you are trying to do.  Keep it pretty General.  You specified a number of steps?  So maybe the top level should be a State Machine, or a message in queue manager.  Describe you something that works at a constant speed, generating data that you have to manage "on the fly"?  Maybe it's a design of producer/consumer.

  You have a lot of initialization?  Put in a Subvi, bring the 20 son out in a bundle (it's "Boss-word" for a Cluster).  Your main program must have a few loops, with values that persist (possibly changing) during the program running in Shift Registers near the top of the loop, with tables and Clusters used to keep related items "consolidated".

  Not too bothered by the size of your routine - I recently downloaded a monster 50-monitor the Forums (I did not even try to understand), up to 6 monitors is nothing!

  Let "encapsulate the function" and "hide details" to be your guide in the reflection on the creation of the screws.

  Bob Schor

  To develop on the analogy of Bob, each talking point can be a Subvi.  In other words, code group associate subVIs.  The advantage of this is that it is much easier to solve problems because all errors will be localized to a Subvi.  Errors no longer Chase around the block diagram.  I guess you can use your current VI as an example of what NOT to do on the block diagram.

• Index Array icons: Palette and divergence of block diagram

  Hi all

  Why are the Index Array icons discrepants?

  There is a small difference between the two of them...

  ... That's how you see when you look at the table Palette...

  

  ... But this is how it appears when it is placed in the block diagram.

  

  Compare yourself:

  

  Is there a reason for this? I don't really know. I also looked for a thread about this, but I have found no.

  Have you ever noticed this?

  BTW, I'm using LabVIEW 2012 SP1.

  Best regards

  Hi João,.

  so to summarize:

  -l' icon changes when wiring to a 2D array entry rather than a 1 d of entry table

  -l' icon changes too much wiring when a 2D array input and, in addition, all the wiring index entries

  -l' also shows context help leaves how to index more than one element of an array

  -the range (maybe) shows an old version of the icon

  There is more than a simple icon fixed to IndexArray function, but that only one version is displayed. You will notice this behavior for many more functions...

• block diagram window becomes higher in win7 64-bit using LV2011 32-bit sp1

  I have a strange problem and I wonder if anyone has ever seen this behavior. Often, when I go to the block diagram window, it will become the top window that is it is located at the top of all other windows including LabVIEW non-windows! I have to close the VI and really open to fix the problem. I see this on 3 machines, all the dell of m6600 laptops so I think it's maybe a graphics driver issue. Any ideas?
  Thank you
  Michael.

  Tori,
  I confirm that this problem can be solved by removing the Dell Premier color utility that installs with the driver dell put on hardware compatible color first. The question of the window occurs when LabVIEW works so there is some kind of conflict. Anyway, problem solved for me.

• Deleting the definition of Type casuses control a lot of misreferences and program in the block diagram errors

  In LabVIEW 2010, I have a Def Type control i.e. a Cluster with several other controls within the Cluster. Apparently, the references to the controls in the block diagram are based on the order that the controls have been added to the Type definition command. The side effect of this is that if a control is removed from the command of Type definition, many of the done Variable reference in the block diagram or now either broken, or worse still, refer to wrong control in the Type definition. These problems are quite difficult to find and fix.

  Comment: If you create a control of Type definition and make a Cluster. Now add any controls to the Cluster in an order, let's say A, B, C, D. Their types does not matter. Now use the Type definition in one or more controls on the front panel. In the block mark references to controls inside the Type Def would control on FP. Now return to the Type definition and remove the command B of the definition of Type. Now, lots of errors appear. Broken links. But worse still, you see old references to B that now refer to C and old references to C are now referring to the old references to D and D are removed altogether, etc..  This side effect is much more errors, broken links and misreferences than expected otherwise.

  How add and remove controls anywhere in a Cluster in a Type definition, at will, without creating a whole bunch of errors in program, broken links and misreferences for controls in the Type definition that have not changed?

  
  

• HOWTO call "n" independent instances of 'Decimate (continuous) .vi"without putting instances of"n"of the VI on the block diagram?

  I have a double 2D chart I want to decimate continuously using the ".vi (continuous) Decimate" located in the range of Signal Processing. This VI is set on reentrant preallouee clone because it uses a FGV to save the State of the call to.  What I could do, but do not want to, is having a huge index table and wire 20 + 1 table of DBL to 20 + unique VI instances decimate to ensure that each have their own data space and no 'cross-talk' doesn't happen, then 'picture of generation' all back after the fact.

  I'm almost certain, there is a much cleaner way to do it with only one instance of unique block diagram of the VI decimate using techniques of the call by reference.   I found my way to this link: Preallocated-Reentrant-VI-within-Parallelized-For-Loop that talks about something similar.  After reading pages of four and the detailed help about the function 'Open VI référence' my head is spinning again on what option I want to spend (0x08 or 0x40 + 0x100) to ensure that whenever a slna 2D table come in, each of them is decimated by using the same clone that was used the last time it was called.

  Although the DBL entry 2D array always has the same number of lines, now, it is not always in the future this number and ideal would not force me to create several references strictly typed in VI decimate that will have to change as grows the number of rows in the table 2D static DBL.

  Anyone ready to set up an example VI that takes an array 2D arbitrary of DBL as input, decimating each line using the same clone independent of the "Decimate (continuous) .vi" and outputs the newly decimated 2D Array of LDM?  Assume that each line uses the same factor of decimation and 'Sprawl' set to False.

  Necessity is the mother of all invention and since it upsets me when I read a post that has a similar problem with no resolution, I felt compelled to post mine here.   I'm sure it's better I can do within the current state of LabVIEW.   The only question I have is what happens if I put the call by reference for loop be parallelizable?  That trash completely the nature of 1 to 1 of what I intended?

  

• Remote debugging active but no access to the block diagram

  I have an executable running on a target that I want to debug. I enabled debugging in the build properties, I enabled debugging in vi properties. I can connect from the development computer to the exe.

  But the option to switch to the block diagram is simply not there (see photo). I know I am a first not who has this problem but I couldn't find an answer.

  Without being able to see the block diagram, a 'debug function' is totally useless!

  If anyone has an idea it would be greatly appreciated. Thank you

  

  Hi peter,.

  It is a known problem and a request for Corrective Action (130070 CARS) was created and reported to the Department R & D. looking at through the notes in the CAR, he must fix it in LabVIEW 2012.

  Workaround solution:

  Debugging applications with menus on bar