Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 01/19/2021 in Posts

  1. A new chapter in the NI saga? Found in a recent SEC disclosure (I was trying to figure out whether the slow increase in NI stock value since last November was due to something else than the recent announcement that they were firing 10% of their employees to increase the shareholder happiness): "On January 3, 2021, Carla Pineyro Sublett, the Company’s Senior Vice President, Chief Marketing Officer, and General Manager of the Portfolio Business, and a named executive officer, notified the Company of her intent to resign from the Company, effective February 1, 2021, to pursue other oppo
    2 points
  2. But the real story: Harrison Ford was sick and so the director just off-the-cuff said to just shoot the guy. A big sword fight was originally planned, but instead we got one of the most iconic movie moments.
    1 point
  3. I have a whole directory in my toolkit called "Windows Specific" which is for VI's that call the Win32API. But unarguably THE most useful for me is the Win Utils I originally wrote in LabVIEW 5 and still use today. Windows API Utils 8.6.zip
    1 point
  4. The potential is there and if done well (which always remains the question) might be indeed a possibility to integrate into the import library wizard. But it would be a lot of work in an area that very few people really use. The Win32API is powerful but not the complete answer to God, the universe and everything. Also there are areas in Windows you can not really access through that API anymore. In addition I wonder what the motivation at Microsoft is for this, considering their push to go more and more towards UWP, which is an expensive abbreviation for a .Net only Windows kernel API without
    1 point
  5. My informations from inside NI is that this is largely untrue. NXG team will be re-assigned to other projects and a large part focusing on non-Windows OS support 😮 I don't have much details but different sources corroborate this.
    1 point
  6. here a post on how to update to the last sql libraries (3.34) to run successfully that example on NI RT
    1 point
  7. You got it right. "Delete branch" will delete the branch on your fork. It does not affect the clone on your computer. The idea is that every pull request has its own branch, which, once merged into master, can safely be deleted. This can indeed be confusing if you are used to centralized VCSs. In Git, any repository can be remote. When you clone a Git repository, the source becomes remote to the clone. It doesn't matter if the remote is on your computer or on another server. You can even have multiple remote repositories if you wanted to. You'll notice that the clone - by def
    1 point
  8. - LVCompare and LVMerge should be unlocked with the LabVIEW base edition. Or even better, an open source merge and compare tool could be released to the community.
    1 point
  9. I have a theory for what a good UI for GIT would look like, and it is a bit different from the existing ones. I think there should be a picture of the current state of the world. You draw a picture of the state you want. Then the tool generates the command line commands that get you from A to B. This serves two purposes: rather than taking an action and then seeing if that did what you want, it puts the UI in charge of figuring out how to get you textually what you're specifying graphically. Second, it shows the user what the commands are that it is executing so that you figure out "oh,
    1 point


×
×
  • Create New...

Important Information

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