Jump to content

Forcing palette editor not to save edited palettes to user directory


Recommended Posts

I have this memory that there was some way (like an ini key) to get the palette editor to save editted palettes 'in place' in the main installation directory and not into the user's LabVIEW Data folder.

 

Does anyone know how to do that...?

Link to post
Share on other sites

I don't really have much experience with editing palettes, but what you might be talking about is the readonly.txt file in the menus folders. If you rename it, LV should allow you to edit the built-in palettes.

Link to post
Share on other sites
http://forums.ni.com/t5/LabVIEW/How-do-I-control-the-location-of-palette-files/td-p/929187]According to Darren[/url] it's InternalPaletteEdit=True.  However I would back up your menus directory first in case you want to revert.
Thanks - that's the one I was remembering being told about! I'm setting up a machine that will be used to be an image for several machines used for teaching and wanted to make sure I really changed the palettes for all users.
Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Similar Content

    • By X___
      The title is made up, but explains what I have been experiencing for years, hoping that it would be fixed in the next version, but it never has, so I am starting to suspect nobody is caring or possibly maybe nobody even noticed it?
      Anyway, the symptoms are:
      when I drag a VI (from either a palette or from the icon of an open VI) into a target VI's diagram, I am frequently encountering this odd and annoying 🚫 symbol where my cursor is (it's not red and it is slanted the other way, but this is the closest emoji to the real thing I could find), instead of the "androgynous" cursor (a mix of ♀️and ♂️) which tells me that I am going to copy that object where the cursor is.
      I would move the cursor around, seeing a 🚫 wherever I go, until I would fleetingly grasp a cursor with the + index (the "androgynous" cursor) over some random location, and then, painstakingly try to go back to that region to find the sweet spot (pixel really) where I am able to drop the VI. Of course, once dropped on the diagram I can move the VI anywhere where I was forbidden to drop it during my initial attempts.
      That's got to be the most annoying bug in a graphical programming environment ever...
      Am I the only one to experience this?
      I am using 2019 SP1 64 bit, but that has been around for several versions already.
    • By wuuuuuud
      Well, in my project I *have to* get data from another program via the clipboard. And the data transferred could be as large as several MB. When another program send the data to the windows clipboard, the whole labview program will stuck for several seconds or minutes,depending on the data size. Meanwhile, the memory Labview using increases slowly in the task manager. This occurs every time, no matter whether a VI is running or not.
       
      So, I guess the Labview is monitoring the clipboard changes and always trying to parse the clipboard data to the format of a FP control or something else, which could be time-costly.I'd like to know if anyone here have experienced the same issue or if there is another possible reason or solution for the stuck?
       
       
    • By John Lokanis
      I have been seeing some weird behavior and was wondering if this is a known issue or if I have discovered something new.
      I have two projects that share several libraries and classes.  One is a client application and one is a server.  In order to test my code, I need to open both projects at the same time and run the main VIs.  When I open the projects, the common libraries and classes are locked and I cannot edit them.  So far, this appears to be normal.  Where it gets strange is when I close one of the projects.  If I have run the VIs to test something and then stopped them, closing the owning project of one of the main VIs DOES NOT cause the VI to also close.  The correct project name is still indicated in the VIs window (lower left) and the project is clearly closed but the VI is still hanging around.  The second thing that is weird is the common libraries and classes remain locked. Even closing the other project and returning the to the start-up screen does not correct this.  The only way to edit those files again is to close LV completely and then reopen it.
      This is getting a bit tiring and I am just starting to develop this project.  I am working with LV2012f3 but have not yet tested this in the 2013 beta.  (I really do not want to port the whole project over at this time).
       
      Any thoughts?  Anyone else seen this?  I checked the known issues link and did not see anything related.
       
      http://www.ni.com/white-paper/13993/en
       
      thanks,
       
      -John
       
    • By bbean
      Here is an interesting talk by Bret Victor. He has designed experimental UI concepts for Apple and others. To me its interesting to see how text based languages could catch up to LabVIEW's graphical style and even exceed it with instant visual feedback. Its also interesting to see how the IDE in any language could be improved.


      The video goes much deeper than programming languages and delves into life principals. Well worth the watch.
    • By Ton Plomp
      On Stackoverflow someone posted a question on how to recover a VI's password
      To my surprise there was a thorough answer containing two methods:
      Look up the stored MD5 hash in a VI file
      I can understand this, and am not really concerned, this might be a valid method if you know a password is from a given list (choosing a password from a dictionary is dumb anyway).
      Modify the LabVIEW executable binary to ignore the password checking.
      I have not tried this on LabVIEW 2011, but if this works it basically means that passwords are just a sign that says 'Do not trespass'

      Can anyone verify the LabVIEW edit function in 2011.
      On a more general discussion, does this troubles you anyway?
      Ton
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.