Re : How to use writekey.vi to write Keys ONLY

[billko]

BTW - there is an option to write a raw string - no quotation marks.  I hope you didn't modify the LabVIEW write key code to work around your issue.

[Ubujuq]

Hi , I did modify Writekey vi to remove addQoute and rewire it, and it work for me.

Thank You.

JDiaz

[RavensFan]

Until you do a project where you need the quotation marks!

Or until you take this project and run it on another PC where the vi.lib files weren't hacked to get rid of the quotation marks!

[Darin.K]

---

@billko wrote:

BTW - there is an option to write a raw string - no quotation marks.  I hope you didn't modify the LabVIEW write key code to work around your issue.

---

The raw string option only controls whether or not the string is escaped, there are quotation marks either way.

I needed this exact modification (and I actually changed it so the raw string option did not add quotes).  To achieve this I had to copy the entire library and now maintain my own separate version outside of vi.lib.  The simple fix would be to add a new version of Write Key (String).vi, but all of the subVIs are private to the NI library.  That is why I think long and hard about anything I mark private, it simply cripples code reuse if misapplied.

[Ubujuq]

Well, I did my own WriteKey.vi w/o quoted marks,so this will part of my own application which finally will be an executable file.

JDiaz

[billko]

---

@Darin.K wrote:

---

@billko wrote:

BTW - there is an option to write a raw string - no quotation marks.  I hope you didn't modify the LabVIEW write key code to work around your issue.

---

The raw string option only controls whether or not the string is escaped, there are quotation marks either way.

I needed this exact modification (and I actually changed it so the raw string option did not add quotes).  To achieve this I had to copy the entire library and now maintain my own separate version outside of vi.lib.  The simple fix would be to add a new version of Write Key (String).vi, but all of the subVIs are private to the NI library.  That is why I think long and hard about anything I mark private, it simply cripples code reuse if misapplied.

---

I must have mis-remembered that.  Doesn't surprise me.  Sometimes I have a "creative" memory.