Jim Kring

Hi Paul, You might also want to take a look at Fowler's Supervising Controller and Passive View patterns (which he split out from his MVP pattern). Good luck, -Jim

QUOTE(Justin Goeres @ Dec 18 2007, 07:06 PM) No, I don't thing we need tagging of posts. Speaking of tagging, check out the tagmaps technology that yahoo is working on. It shows a tag cloud overlayed on a map. It uses a cool algorithm to only show you tags at the resolution you are looking at. The further in you zoom, the more specific the tags become. For an example of cool stuff you'll find, check out Yoda in the Presido.

QUOTE(Tomi Maila @ Dec 12 2007, 11:50 AM) Yes, that works for me too. I mentioned that at the bottom of my original post Cheers,

It looks like Michael has renamed the forum to "Object-Oriented Programming". Thanks, AQ, for the great suggestion (and interesting tangential debate). Cheers,

QUOTE(Aristos Queue @ Dec 8 2007, 11:37 PM) Whether or not a tool is object-oriented is not a black and white issue -- tools are object-oriented on a continuum of varying degree. If we think abstractly (which, as we know, is an important skill for object-oriented analysis and design) then we will notice that Functional Globals exhibit shades of the following object-oriented concepts: Class, Object, Encapsulation, and Abstraction. We will also see that the other two concepts of object-orientation, Inheritance and Polymorphism, are not found in Functional Globals. As such, Functional Globals are a tool (albeit not 100% object-oriented) for implementing some object-oriented software designs. There are almost no object-oriented tools (LVOOP included) that do not limit software developers due to the constraints of the frameworks and the histories of the tools they are written in and the developers who created them. Certainly, Functional Globals are not the best object-oriented tool for LabVIEW developers, but that said, you'd be hard-pressed to find another object-oriented programming technique in LabVIEW with such wide-spread adoption and successful deployment. Does acknowledging that Functional Globals have object-oriented qualities and understanding their importance today and in the history of object-oriented LabVIEW techniques really make me a Neanderthal? Maybe. But, doesn't the analogy of pounding and poking beg for a Freudian interpretation? "Tool envy" comes to mind Kring out,

QUOTE(Aristos Queue @ Dec 8 2007, 05:12 AM) Functional Globals encapsulate data and functionality in a singleton by reference "class" -- they are one of the first object-oriented programming techniques employed by LabVIEW developers. Check out LabVIEW for Everyone, 3rd ed. Appendix D (pp. 903-912) for more info

QUOTE(Aristos Queue @ Dec 7 2007, 07:00 PM) Nor would it help folks who search for "GOOP", "OpenGOOP", "dqGOOP", "Functional Globals", etc. Maybe it would be good to have some subforums or categories.

QUOTE(Aristos Queue @ Dec 7 2007, 03:37 PM) Nay. LVOOP is just one aspect of object orientation in LabVIEW. I propose we rename GOOP forum to "Object-Oriented Programming" or just maybe just "OOP". However, maybe there should be a LVOOP subforum, but I'm not really sure yet. That said, if you give us by reference LVOOP then I'll give you all my support on this proposal

QUOTE(Michael_Aivaliotis @ Dec 6 2007, 03:00 PM) No, I was just waiting for my 4500 VI project to open and I figured that I would kill some time by messing with crelf.

2007 isn't over yet

QUOTE(crelf @ Dec 6 2007, 11:27 AM) I took that to mean that I was the problem.

QUOTE(Aristos Queue @ Dec 6 2007, 07:03 AM) Hi AQ, BTW, this project is the same one that Jeff W. was helping us with. We generated several CARs (including CAR 4EUFQ954, title: "Jim Kring problem" - some of the bugs we're finding are hard to describe with words). As Philippe mentioned, this project has about 4500 VIs and has a lot of proprietary stuff in it which makes it tough to send stuff to NI. However, if you or Jeff want to come visit San Francisco, we'd love to show you our workflow and pain points. Thanks, -Jim

QUOTE(rolfk @ Nov 27 2007, 12:29 PM) Hi Rolf. Thanks for the help. That works fine for me, too

I have been playing around with the possibility of using .NET to read and write TIFF files. I've hit a little bit of a wall when trying to configure the encoding parameters such as compression and color depth. I followed the example code on the MSDN website here. However, I am getting errors when I try to run this code in LabVIEW. I've been able to isolate the error to the encoderParams argument of the Bitmap.Save() method. However, I believe that I am constructing this argument properly, per the example code. Has anyone else played around with this? Download File:post-17-1196143600.zip

I have been playing around with the possibility of using .NET to read and write TIFF files. I've hit a little bit of a wall when trying to configure the encoding parameters such as compression and color depth. I followed the example code on the MSDN website here. However, I am getting errors when I try to run this code in LabVIEW. I've been able to isolate the error to the encoderParams argument of the Bitmap.Save() method. However, I believe that I am constructing this argument properly, per the example code. Has anyone else played around with this? Download File:post-17-1196143600.zip

QUOTE(Tomi Maila @ Nov 21 2007, 12:28 AM) Actually, I think that it's gmail that does this. I'll bet that hviewlabs copied and pasted that text from his web browser.

QUOTE(Tomi Maila @ Nov 21 2007, 12:28 AM) Actually, I think that it's gmail that does this. I'll bet that hviewlabs copied and pasted that text from his web browser.

QUOTE(Tomi Maila @ Nov 20 2007, 03:46 AM) And refnums, too

QUOTE(Tomi Maila @ Nov 20 2007, 03:46 AM) And refnums, too

QUOTE(Tomi Maila @ Nov 20 2007, 03:46 AM) And refnums, too

QUOTE(Norm Kirchner @ Nov 12 2007, 01:12 PM) I noticed this too. Unfortunately, even when different control types implement Size, it appears that they do not inherit it. So, there is no generic "Size" property. We'll have to create a type-check>>down-cast>>size-setter VI -- and, this doesn't exist. -Jim

QUOTE(Michael_Aivaliotis @ Nov 12 2007, 12:33 PM) Not really, I've played around with it inside of panes and it doesn't always work as expected. However, I'm testing in 8.2. Maybe this is fixed in 8.5.

QUOTE(Norm Kirchner @ Nov 12 2007, 07:59 AM) Hey Norm, Is your VI very general purpose? Want to make it general purpose? Need help? I'll probably end up implementing this for myself and if you've already got a head start, I would be happy to add my contributions/improvements and post them to LAVA as a BSD licensed VI. Thanks, -Jim

I have a Tab Control with several pages. Each page has one and only one control/indicator. I would like to configure each tab, such that the one control/indicator on it takes up the entire page area of the tab. For example, I have the Tab Control on a VI's pane, and the tab control is set to Fit Control to Pane. As the pane resizes, so does the Tab Control (and therefore its pages resize). I want the control on each page of the tab to also resize, so that it always fits the entire page area as the Tab Control resizes. A Fit Control to Tab Page option might do the trick.

QUOTE(crelf @ Nov 8 2007, 04:02 PM) I thought you guys were just speaking german, with all those really long strung-together words