Jump to content

Val Brown

Members
  • Posts

    754
  • Joined

  • Last visited

  • Days Won

    2

Posts posted by Val Brown

  1. I can't share the VIs I am using, but I will give you the core functionality of Sqlite VIs that Import-Dll creates. From these VIs you can see how to change the VIs created by Import DLL. Let me know if you have any questions.

    I have included the Sqlite3.dll, but you should've already have this Dll if you are interested in Importing it to LabVIEW :-)

    OK, I've tried opening this ZIP and I get an error message about Searching for: <userlib>:|SQLite\Custom Controls\sqlite3.ctl. Can anyone help with this?

  2. Of course then, if you do that, you lose the easy, already built-in extensibility of the other drivers.

    Again this is a paradigm argument not a rational discussion (meaning the original posted video). This is someone who believes the grad school hacker of the good ole days is the real hero and should be supported in all ways, but esp in terms of open source software and hardware. But perhaps most importantly in gaining and using real, true insider geeky knowledge -- the kind that comes from HAVING to make a really cheap hardware solution work in a limited budget environment, not a real-world production environment.

  3. Certainly would be nice to have XNodes made "official". One thing that would be nice to do would be to write a reference example XNode that showed off as many features as possible in properly documented code.

    I'm intending (as time permits :rolleyes: ) to reimplement the OpenG Array tools as XNodes so that one doesn'thave to have loads of polymorphs for each and every type of array.

    In the same vein as Shaun, and beginning to push the off-topic envelope further, I get concerned when I hear about OpenG and other 3rd party tools seeming to become "coin of the realm". Yes, I'm an oldline LV hack (and an older line C/Unix hack -- and I DO mean C), but I don't like having to rely on 3rd party tools that are tied to certain non-NI implementations. For my purposes it works far better to use only NI "tools" and, no, at this point I haven't found scripting to be directly useful; so Shaun that club has at least doubled in size.

    On the other hand, would it be useful to ALL (or most) LV users to have xnode functionality more exposed -- perhaps. I don't know. Was it useful for scripting to be officially released -- again, perhaps. But not if the outcome of that release is more 3rd party tools instead of one integrated environment that has a large, multi-use/multi-user base. After all, I'm STILL using the Blowfish implementation based on a 1998 CIN implementation! It was the ONLY option for a long time and still remained the best option -- for me (yes!) -- after other options became available. I really don't want to see similar patterns repeated.

    And that's why -- despite the HIGH quality of JKI tools -- I always ask: Is there a way to implement "x" WITHOUT having to use OpenG or...

    OK, I'll slink back into the shadows...too much work to do.

  4. I wrote a code which opens an avi file that shows how to work with one of our instruments. I made an Activex container in front panel and inserted windows media player in it. It works very well but the issue is every time it opens the avi file, it expands the container frame and shows the video in a larger frame. I want to fit it in it's own container frame which i have put on front panel. I tried a lot with property node and property invoke stuffs to figure it out but i didn't find the solution!!! I would appreciate if anybody could tell me how i can fit the video file playing in it's own playing-frame on my front panel.?

    This is a known bug for which a CAR was filed several years ago. NI has chosen to NOT address this issue and has put the CAR in whatever their equivalent of a "round file" is.

    AFAIK, your only solutions are:

    1. create a container for WMP in another language (eg VB) and reference that object in the usual ways

    2. write code in LV to resize the WMP container to a known size after every load or equivalent operation in WMP.

    Of course a third option it to try to push NI about fixing this but, even if that succeeds, nothing will happen until LV 2011 at the earliest and most likely your project won't wait that long!

    val

  5. As justingoeres would say: "It's About Time!"

    Hmmmm, wasn't that Dr. T starting that? And now "it's about time" for it to be put to bed I think.

    Congrats Mike and all of the JKI team! It sounds like there is finally going to be a real working collaborative relationship between JKI and NI -- hopefully OpenG won't be far behind. Uh, yeah....."it's about time". Now I've said it for this, uh, time (damn)...

  6. Are you sure you have 32bit LabVIEW installed and not 64bit?

    Yes.

    What do you mean with the DLL returning 0 for the reference while the Automation Open crashes? Is this DLL an ActiveX DLL or a normal DLL, accessed through the Call Library node?

    Yes it's an ActiveX DLL so accessed via Property and Invoke Nodes.

    Otherwise there might be a problem with registration of your component/DLL.

    I don't know what the problem could be re: registration as the component exists, is registered, and, when used on the same system, works fine with the already built (in 8.6.1 LV) EXE. The problems ONLY occur in the development environments: with LV 2009 on Vista 32 I get the 0 return from the Automation Open, whereas on W7 64-bit I get LV to crash while trying to "use" the Automation Open.

  7. I have a third party DLL that was crafted in 2006 for 32-bit WIndows. I have a legacy built LV app (using 8.6.1) that references this DLL. The 32 bit EXE works correctly in W7 64-bit; however, when I try to access the DLL in my development environment (LV 2009 32-bit running on W7 64-bit OS) I consistently get a 0 for the value of the reference. Interestingly the Automation Open primitive crashes LV.

    Any good ideas?

  8. Yer, I have seen the layout change internally and I don't like that.

    But you can't have your cake and eat it too.

    Whilst, a .llb layout is very handy for relative calls, encapsulating libraries and classes etc... inside the build (exe) is far more valuable IMHO.

    However, its nice that you have the option to use the 8.x Build Model.

    Otherwise porting up all my older code would be a nightmare. throwpc.gif

    It HAS been a nightmare for me.:frusty:

×
×
  • Create New...

Important Information

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