Jump to content

ShaunR

Members
  • Content Count

    3,958
  • Joined

  • Days Won

    200

Everything posted by ShaunR

  1. Nope. You may want to extend that courtesy but it isn't required for BSD.
  2. Perhaps this makes it clearer. What you are doing: What you want to do:
  3. The FP control is set to "Include Data Type" if the property node is "strict" and will be a boolean output from the property node. You will see a red cross in the bottom left corner of the control in this state. If "Include Data Type" is unchecked, there will be no cross and the output of the node will be a variant as no type information is defined for the control..
  4. The software was never productionised and released due to lack of interest.
  5. AQ has been looking into this for me offline (Thanks AQ) and managed to replicate the issue I was seeing. Addig a delay resolves the issue (which I plan to put in the known issues since it cannot be resolved internally in the xControl) AQs explanation of what is happening: He also said that the problem goes away if source code is separated from the VI (not available in 2009). So. I'll do some more testing and then release the xControl.
  6. Error 2250 is the windows error code for "This network connection does not exist.". It seems consistent with what Rolf is saying about the function.
  7. It's a conjugation. I think Americans are the biggest perpetrators especially for "setted". They do other funny stuff like leaving out letters and putting dates the wrong way round
  8. I just post something along the lines of "can't find it right now" and usually someone with better organisation than me finds the link. Damn. giving away all my secrets.
  9. My OCD is when people type "casted" as the past tense of "cast". Not helpful, I know but It drives me nuts! I'm the same with "set".
  10. Well. I didn't even get one like, let alone 10 points
  11. Apollo 13? (It's a NASA saying)
  12. You can use the Path to Array and then slice out whichever parts of the path you need and concatenate back again.
  13. They seem to have that covered. I would be more worried that because it is .NET; the default is UFT16-LE so any strings from property nodes could be that instead of ASCII. Things like the version/serial numbers, label text, class names etc. If that were the case, I could see a lot of utilities breaking.
  14. When I wrote Passa Mak I went through all this. It replaces Captions and Tip Strips and anything else that has a text property on-the-fly but the inevitable support required to allow people to use languages like Japanese or Chinese was just rediculous-so I didn't. The real problem was filenames, though. How did you resolve that?
  15. You'd think I would've known that since I produced a toolkit to do exactly that...lol.
  16. For JSON I use SQLite nowadays since all my apps have it (and it's searchable with SQL). Other than that. I don't use OpenG at all and, as far as I can remember, JSON was the only reason I used type functions. I'm using 2009 so it's not using the newer ones and the only thing I can think of could cause a problem is if the class names would be UTF16. I could easily work around that, though. I think anyone that has used variant look-ups as dynamic fast-tables would be shafted, though.
  17. You can get it to display Japanese under certain conditions (ini setting and Force Uncode Text on the control) but it is permanently "stuck" so you end up with spaces between chars for ascii. It also requires converting the to UTF16-LE via windows calls (hence you need the code language packs) so it is not cross platform and it doesn't work at all with filename controls or file functions.
  18. If you want to display Japanese, you cannot on an English version of Windows - you just get question marks.
  19. Thanks for doing the leg-work. A) Is a good thing but I would have preferred ASCII as the default for campitibility. I wouldn't relish going through an already working application and having to explicitly change all the nodes. The only time you would know if you'd missed a node to change is when data intermittently gives incorrect results. B) I don't really care about since I have only used it once or twice mainly for JSON. The other question is; can it actually display UTF8/16? We can already deal with UTF8 with the primitive. What we can't do, currently, is display it on non, language specific OSs.
  20. Is this all strings and if so how do functions such as TCP/UDP Read/Write and Byte Array to String/String to Byte Array operate?
  21. Um. Can't we? If you select the objects on the front panel and press the "Reorder" button in the toolbar. There is a "Group" option. That will group the selected controls and you can move them around as one unit. Maybe I'm just misunderstanding what you are asking.
  22. This is a test harness I'm using. It is the VI loaded into the sub-panel (Example1.vi) that invokes the save dialogue when this VI (Example2.vi) finshes executing. It also happens if the the Abort VI button on the toolbar is pressed. (auto dispose ref = true makes no difference if that's a criteria).
  23. It is loaded with Open VI Reference. The Explain Changes" dialogue states that it is a cosmetic change (A front panel object was resized). My current suspicion is that it is linked to the "Fit Control to Pane" setting of the xcontrol on the host VI and/or the facade (which the actual control is also set to). I've at least now ascertained that it also happens in normal sub-panels too and is repeatable. Maybe I should just publish it with a known issue - something I have always hated to do. Then at least others can fiddle with it.
  24. ShaunR

    LabVIEW Memes

    am I doing this right?
  25. I think so. Well. I know so but I'm unsure of the mechanism since it is an xControl on a VI that is loaded in a sub-panel of another xControl (if that makes sense-it's nested). When exiting, the host VI (loaded in the sub-panel) wants to be saved. I can stop it by not updating the display state of the xControl on the loaded VI host, but then the facade doesn't update properly. Additionally, it doesn't seem to be every time; just sometimes which is proving to be a barrier to finding a work-around. If it's not loaded in the xControls sub-panel (even a normal subpanel), then it all works as intended. I have, since, thought of a couple of things to try, but it'll have to wait until I can get round to it again. Amen.
×
×
  • Create New...

Important Information

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