Locallyowned and owner managed for over 39 years, Lindy's Subs & Salads has been providing La Crosse & Onalaska with the finest subs and salads in the area. Enjoy a delicious, made to order sub, served on fresh baked bread, with the finest meats & cheeses, and the freshest veggies available. Or select one of our delicious salads, made from fresh veggies hand cut every morning. Call us for the quickest most reliable delivery in town. Or dine in at one of our two Coulee Region locations:
Give Lindy's a call for your catering needs. We have fresh, made to order party platters of all our subs, salads and wraps. Perfect for business meetings, office parties, birthday parties, picnics, sales luncheons, wedding day lunches or anytime you need fresh food fast!! We can do it all.
I've been working with Access for a while now, and although I understand the obvious benefit of a Function over a Sub, been that it can return values as a result, I'm not sure as to why I should use a Sub over a Function. After all unless I'm mistaken; Functions can do everything Subs can do?
The above is a handy tip, since then you can highlight 10 controls on a form, and type in the above expression and you just assigned the above function to those 10 buttons. You cannot do the above with a sub.
Another significant difference is you can utilize these functions in SQL. This is a truly fantastic ability as then you can have code "run" for each row of a query. And this means you can extend the ability and functionally of SQL.
And even more interesting is when using custom XML for ribbons in Access, then if you use a function() expression for the "on action" attribute then you can avoid the need for ribbon call backs. Even better is the ribbon will call those functions() in the current form, not a public code module like you MUST do with ribbon call backs.
So this is basic and simple difference between a sub and a function, and I dare say those who have written computer code will in just about any programing language will instantly realize the above significant and useful differences between a subroutine and a function.
The main difference is not only the return value, it seems that subs are faster than functions(at least in .net) because the MSIL code of subs is much shorter when no value is returned. so overall subs are faster when no value is returned.oh i've just found a great source for it (talks about .net), maybe you would like to read further about it- Functions vs. Subroutines
I'm not absolutely sure, however, I think subs are faster than functions because the variables of a subroutine are defined upon creation of the subroutine and are accessed by referencing the memory location. Functions must allocate memory space every time they are accessed.
Subroutines modify the variables in the calling code and functions leave them intact. So a subroutine can provide several modified pieces of information to the calling code (as many changes as there are variables, including arrays) but a function can only provide one answer at a time for the values that are passed to it. Because of this difference, if it is important that a variable in a subroutine does not change its value, one must assign the value to a temporary variable defined within the subroutine itself.
First way, send out requests for information to helpers and they will return with the information for you. so you remain in control ie all info is flowing back to you and you are deciding what to do next if any. this is more of the centrally controlled environment. this is the essence of 'function' in vba
Second way, divide up work into separate tasks and assign responsibility to your helpers to finish the task for you ie actual work is performed here by helpers in contrast to just gathering info. This is the essence of 'sub' in vba.
So think of what to do if code breaks. with function calls, you concentrate on the central command to look for reason of failure. With sub calls, you have to run into each sub's work and find out what they did wrong.
Of course, you can screw up the purpose and have functions do work and subs just get info but that would just be really confusing when things break! Oh but you cant do that, read this link - , which states that Excel forbids functions changing cell values and subs being called from cells.
I found one other difference, at least on Excel but likely other Office apps. If you want to customize the ribbon by adding a button to launch a VB program, when you choose Macros in the "Choose commands from" dropdown menu, it lists any Subs in your code but not Functions. Note that a Private Sub will also be hidden from the customize ribbon selection, as will a Public Function.
I am new to ION. I am used to using a console that has the ability to record looks stacked on top of each other on each fader. When that fader is raised all I have to do is tap the bump button and the next look plays. I can tap as fast or slow as I want and it will continue to advance stack by stack, over and over and over. That fader can be set to reset to stack 1 each time it is brought to 0 or to remain at the last look played back. I can also tap another fader bump button while one fader is already up and it will flash to that second look then when I release the bump it will snap back to the one already playing. Because of that I can keep fader 24 (example) up all the time as a "between songs" look so that when all other faders end up turned off 24 will automatically be playing.
The console has a total of 24 faders with ...# pages. I seldom to never used that feature in the theatre setting. In the theatre I recorded cues and ran it like the ION, using the GO. I ALWAYS used the bumps for concerts. Having literally hundreds of pre-recorded looks I could run the show strictly from that and never need to make changes on the fly. All I needed to know in advance is if the band songs were slow, med or fast and I could plan on what to play back based on that.
My first question is am I on the right track? Can I just make a boatload of different cue lists and store them each on different faders then play them back by raising that particular fader and tapping them to change them. I assume I also need to make proper settings on the bump butttons.
Second question is because I will always be all over the place playing back looks in concerts, should I run the console for concerts in the Cue only mode rather than Tracking and keep Tracking for Theatre.
No, it will not function quite like the "other" console, especially as what the fader is doing is replicating the master fader pair - I.E., the bottom bump button is GO, the upper bump button is Stop/Go Back, with the slider is functioning as the manual override for both up and down segments of the cue.
b4 getting too deep and far I created just 3 cues and followed your instructions, putting them on fader 1. So far so bad. Yep they advance forward and backward with go and stop/back but can't see how to shut them off without gotocue out or zero, etc.
Also can't seem to determine exactly what the actual fader really does. sometimes the cues come up full intensity and sometimes they come up at zero. At that point i bring up the fader and it brings the int up to full but when i back all the way out to cue zero they reset everything and keep the shutters open.
If I bring the fader up while they are running then back down then stop/back to cue zero they reset but leave the shutters open. I bring the fader up and the shutters close. I bring the fader off then tap for cue 1 and they go into position at zero int. and cue goes to manual in red. I bump each cue and they advance but shutter stays closed and cue 1 remains red manual. Seems I have to bring up the fader then advance back to cue 1 for the shutter to open and manual to clear. Then I can't shut them off without gotocue again. Ehhhhhhhhhh.
Should you desire manual control of a cue transition, the faders are provided. As described in the manual: "The potentiometer is used to manually complete the cue transition for all parameters. If the fader is operating in a paired mode, the left fader controls the intensity upfade and all non-intensity
parameters, while the right fader controls all intensity downfade actions."
When you use a fader on wing the single fader does double duty and provides simultaneous control of the up and down parts of the cue transition. Thus the only way to back out of a stack is Go to Cue.
In truth, I'm not seeing a method to replicate what you do on the other desk. If you had/have touch screens, I'd be creating presets instead of cues in a stack. I'd them use the faders as inhibit subs to control level, using the presets as the assorted steps of the cue. Gives you more variety as you can change the sequence by varying the presets pressed.
Not in front of a console at the moment, and this isn't something I've really done a lot with, but I believe you can "off" that fader. It doesn't reset it to Q 1, but it should at least release anything controlled by that handle.
Tap Fader Controls. Then Hold down the softkey for "OFF" and press load (both buttons) on the fader you want to Off. You can also muck around with the fader properties of the Cue list. Double Tap [Cue] and select the cue list you are working with. Press the "Fader" Softkey and it will toggle through some options that may or may not work better for you.
Sooo. changing it to intensity master now allows the fader to control intensity which is so far a 100% gain. I know the next release is coming out with some great changes and looking forward to that. I also hear everyone is trying to make the EOS family a bit more concert related and that's also great.
Cue Cue to open the list. select the cue desired. tap the fader softkey (S5) to switch from intensity master to manual master to proportional master then enter to save the desired selection. I changed my one test cue list to intensity master and now I can run any cue on that list basically in blind as long as the fader is down and use that one fader on the wing to control the intensity, just as can be done with subs. That's a big part of my solution. Yep cues don't reset when the fader is zeroed but that's no big deal at all.
3a8082e126