I'm asking for comment or conceptual comment on the changes in Mt4 (600+) regarding the OnTick() versus Start() command, reaching beyond the limited help file details I've found. Not expecting specific answers below in every case, but to try to explain the confusion I'm finding if a couple of paragraphs in reply might help clarify things. Not meaning to rant. :(
Despite having programmed in Mt4 for several years, my experience came from the more forgiving Pascal language and the older pre-600 Mt4 compiler. I have not tangled with Mt5 previously. The update to Mt4 600+ has been frustrating. Many of the help files remain brief and frequently make assumptions to lean examples or no examples at all in some cases.
Is it best to sustain the Start() function in EA's consistent with prior Mt4 design or is the OnTick() function now preferred, if even just in lieu of pending end of life cycle from Mt4 to Mt5?
Is OnTick() an option to be used inside the Start() event for critical process? It's clear the return functions are different and it appears OnTick() tries to remain on the near stack rather than heap. Several things might benefit there in performance, I'm sure.
I don't seem to be understanding OnTick() fully as a "replacement" for Start() or in addition to, but that I'm having to declare most variables static under OnTick() if not global to preserver their statefulness. Increasing exposure to globals wouldn't seem to make sense but the help files I've seen never do say explicitly "do or don't" use OnTick() in a particular manner for EAs, that I've found. It seems by errors emitted, as if OnTick() is reinforcing rigid persistence to the stack, which makes sense, but in an event driven system it's hard at times to picture the degree of stability on a variable in local scope of the start() function competing for next event. In the past, I was not bound to using "static" for the errors which now arise under OnTick() and yet variables not declared static seem to lose persistence at end of scan, regardless of next tick arrival. Or I'm imagining it from runtime assumptions incorrectly. At least in the tester, static declarations appear under OnTick() to even survive a restart, which really surprised me to see on screen Comment()s show up preserved on restarts.
I've always held to the concept to complete a scan before the next tick by efficiency (if possible), but in conditions like Sleep() events, what happens to the state of the current scan / event with Sleep() delay under OnTick()? Does the current event survive and delay letting ticks pass by or end up wiped and cycle next event? I typically have applied a small sleep() period when making calls to the server in the past just as a standard of external events, despite stateful return messaging. I'm guilty of using RefreshRates() sparingly as needed versus MarketInfo() but even that comes to question if statefulness is being sustained / destroyed per event.
I seem to just be missing something conceptual about OnTick() and possibly reading too much into it for lack of a fuller understanding, (at the risk of being told to go find a relevant programming class) :|
I do understand the difference of OnTick() related to indicators or scripts versus EAs, but any literal clarity from the more experienced crowd regarding EAs with OnTick() would be appreciated. I'm sure others could benefit as well from a bit more generalized concept than I've found so far at least.
Thanks much for anyone braving some free thinking replies on concept or specifics, greatly appreciated, (end rant).
Find Shoulder-Head-Shoulder chart patterns easily with this indicator.
Easy to use Customizable colors and sizes It implements breakout signals It implements alerts of all kinds
Indicator Settings - The amplitude represents the size of the patterns to be found. The max. history bars parameter is the amount of bars in the chart to look back.
Less bars to evaluate means the indicator will load faster. Patterns - Choose the colors of the patterns. Breako
Trade Controller provides multiple methods to protect and maximize your profits. This powerful weapon helps you to set the protect and trailing-stop rules on your trade automatically in many effective methods. Once it is set and turned on, you don't need to monitor your orders anymore, the software will keep watching and control your orders with your predefined rules.
It's designed to support multi-protection and trailing strategy: Protect by break-even, protect by percentage, protect by pip, p
This is Gekko's Cutomized Moving Average Convergence/Divergence (MACD), a customized version of the famous MACD indicator. Use the regular MACD and take advantage of several entry signals calculations and different ways of being alerted whenever there is potential entry point.
Fast MA Period: Period for the MACD's Fast Moving Average (default 12); Slow MA Period: Period for the MACD's Slow Moving Average (default 26); Signal Average Offset Period: Period for
This panel represents a demo account for binary options. It will catch an interest of those who start working with binary options and want to practice on a demo account. It will also spark an interest of those who use Meta Trader 5 to get signals for binary options. You can test any strategy using this panel. It supports any currencies available in your terminal. The panel is also very compact, and you can move it to any spot on your chart window.
Now you do not need to look for a broker with a
The script is intended for automatic placing of Buy Stop pending orders, Stop Losses and Take Profits on the user specified levels.
Avoiding unwanted entering a long position in case of false hitting the level as a result of widening of the spread by a dealing center. Avoiding unwanted triggering of a Stop Loss in case a quote pierces a significant level (fractal) without further confirmation with the close price. Setting a necessary virtual order and entering the market in
This indicator is based on Bollinger Bands indicator. It helps user clearly know the Band is expand or contract.
All traders using VSA realize the importance of the volume. Unfortunately, tick and spot volumes are not suitable for these purposes.
I have conducted mathematical calculations and managed to trnsform the price into the volume that is close to the futures one by its ratios. Now, you do not have to wrestle with the question of where to obtain the volume data. Besides, you will be able to use the currency pairs having no futures at all. With RealVolume, you do not need to remember data on each ti
Robust median Renko style indicator for creating custom charts resembling Median Renko, Mean Renko, Turbo Renko and Better Renko candles as well as vanilla Renko with wicks plus PointO charts. This all in one package provides all of the signals needed by day traders, scalpers and even long term traders.
The indicator is an overlay on the main chart so it is possible to utilize one-click trading and order manipulation directly on the custom charts. Visual order placement is a
Tick volume is equal to amount of ticks at the unit of time. There is direct correlation between tick volume and real amount of deals. Every change of the price is a result of a real request to perform a deal. Consequently, fewer requests we have, the less price changes we get, and, as a consequence, tick volume is smaller.
In this case, when big amount of requests appear on the market, price changes happen more often. Big tick volume appears. Tick volume is an important indicator of trad
The indicator is intended for determining the spread and swap size, the distance for setting stop orders and stop losses from the current price allowed and the risk per 1 point in the deposit currency.
The indicator informs a trader about possible additional expenses and profits connected with transferring a position to the next trade session of the financial instrument. It also informs about the spread size and the distance of pending orders, stop loss and trailing from the current price. In a
The main purpose of the indicator is to detect and mark trade signals on the histogram of the Awesome Oscillator according to the strategies "Trading Chaos, second edition" and "New Trading Dimensions".
The indicator detects and marks the following trade signals:
"Two peaks" - Divergence. The signal "Second wise-man" - third consequent bar of the Awesome Oscillator after its color is changed. The histogram crosses the zero line. The signal "Saucer".The indicator includes a signal block th
Cluster analysis of volumes is now available in MetaTrader 5!
The YuСlusters indicator is a professional tool for analyzing the trading volumes. The cluster graph is plotted based on tick data. For the exchange financial instruments these are the volume, type and price of a deal. For the Forex instruments - the real or tick volume (depending on the broker) and Bid price.
There are 6 criteria of cluster generation:
Time interval, the criterion is set in seconds. Price range, the criteri
This is an open interest indicator for MetaTrader 5. It fixes open interest value once per minute and writes it to the file (on your PC). The product works on any timeframe but only with exchange instruments.
This is the Famous Timing Indicator
You can now use the most famous Timing indicator on the planet.
Millionaire Mostafa Belkhayate earned his reputation by using this specific indicator to validate the entry signals supplied by his also famous Center of Gravity indicator on the Forex market. I spent hours, days, weeks to decrypt the formula and now it is finally available to you.
New and Unique for MetaTrader 5
Timing will give you perfect validations for your entry signals. It is the first
FULL Automatic is a fully autonomous trading robot for MetaТrader 5 without configurable parameters.
It is similar to SAFE Automatic robot intended for traders having no knowledge of trading basics. It works in Low, Medium, High and Extremal trading modes.
The EA applies modified versions of well-known strategies, including Elliott waves, following a trend, half-pyramiding, scalping, speculative trading with a double deposit protection. The EA switches the strategies automati
Monitoring and Trend Analysis
This product shows the trend strength levels based on 16 standard indicators, time periods and currency groups.
Depending on the current trend, the indicator colors change from green to red, allowing you to see the full picture.
Whatever your trading method and strategy are, you should always know, in which direction you are trading and what the probability of the trend change is. This indicator will help you answer these questions by calculating the
Fast Copy MT5 allows you to copy trades between different MetaTrader 5 (netting)(hedge) and MetaTrader 4 accounts in any direction and amount, quickly and easily (without loading the system).
Any type of copying is available
MT4 → MT5 MT4 → MT4 MT5 → MT5 MT5 → MT4
* For the MetaTrader 4 terminal — Fast Copy MT4
* For the MetaTrader 5 terminal — Fast Copy MT5
** Before the purchase, you can test the program by downloading the free demo versions — Fast
This is the SMART BREAKOUT EA which allows you to trade HIGHs and LOWs of any hour and any day range you decide.
SMART BREAKOUT allows you to trade favourite strategies such as London Breakout, Day Breakout, US Session, Asian Session.
LONDON BREAKOUT (one of the strategies used by institutions and big players) you can set to trade range between 8-9 o'clock of London time. After 9 o'clock two pending orders are set up. Buy stop for High level and Sell limit for Low level. Once the prices reach
Create your own list of trading instruments Watch list* and combine it with several open charts Link **.
Using this program, a user can create fully-fledged Watch lists, create and delete trading instruments and move through the list.
A selected symbol shows charts in linked windows. Linked windows can have different periods, indicators, experts, trading panels, etc...
Moving through his/her Watch list, a trader an see the full image of his/her strategy in all windows.
A lot of traders use 1
This is an utility for automatic scaling of a chart and making at least 140 bars visible in it. This is necessary for a correct wave analysis according to the Bill Williams' strategy "Trading Chaos". The utility can be used on any timeframe available in МetaТrader 5.
It draws a vertical line through the first bar the calculation starts from. This line allows you to see the probable starting point of the wave sequence along with a sufficient number of bars displayed in the chart. It also makes t
The indicator represents an additional chart window with a lower time frame where bars are combined into groups that are equivalent in time to main chart time frame. Bars are synchronized by the right hand side of the window, i.e. the time of the last bar in the main window corresponds to the time of the last bar group in the additional window. The maximum number of groups is 16; the maximum number of bars combined into groups in the additional window is 256. Limitations on the numbers are requi
The Trade Manager Pro EA is a MetaTrader Expert Advisor that performs position management for you avoiding human errors and enhancing your trading activity.
Amazingly easy to use Trade easily from the chart Trade with precise risk management, hassle free Capital preservation is top priority Let profits run without your attention Enjoy risk-free trades as soon as possible Automatic trailing stops for all opened trades Initial stop losses are placed as soon as trades are
The indicator is designed for easy construction of synthetic charts based on data of various financial instruments. It will be useful both arbitrage and pair trading, as well as for analysis purposes. Its main advantage is simplicity and clarity. Each chart is given as a common mathematical formula. For example, if you want to plot the spread (difference) between EURUSD and GBPUSD with coefficients 4 and 3, then set the following formula:
EURUSD * 4 - GBPUSD * 3
The resulting chart is shown in
Three variables are available for every strategy, any one of them can be disabled, their period can be changed.
type_order=ORDER_FILLING _FOK - order filling type.
ReverseTrade=false — trades opens in reverse direction if true. ExitOnBar=true — trades close on each bar only. spreadcover=false — Spread you pay includes in profit trades. It's like trade with zero spread but you should remember that it can decrease exact match between tester's result and live one. It
Does not support openning multiple orders on a single symbol on MT5
MultiMTCopier MT5Source - new and improved multi-terminal positions copier for your real / demo account, works faster, requires less, flexible in managing and upgrading, new information support. This expert is designed for terminal MetaTrader5 from which the position will be copied.
The EA will copy all positions without delays Additionally integrated notification in situations requiring user attention Butt
This indicator extracts a trend from a price series and forecasts its further development. Algorithm is based on modern technique of Singular Spectral Analysis (SSA). SSA is used for extracting the main components (trend, seasonal and wave fluctuations), smoothing and eliminating noise. Does not require the series to be stationary, as well as the information on presence of periodic components and their periods. It can be applied both to price series and to the data of other indicators.
Reverse TradeCopier Follow can copy trades from an account that is running Reverse TradeCopier Source.
Copies trades from one source (master) account to multiple following (slave) accounts. Allows investor (read only) password for source (master) account. There are no complicated settings and input parameters, everything is easy. Works with different brokers. Works with different quotes symbols (EURUSD_FX, eurusd_m, etc.). Can copy orders from 4-digit quotes platform to 5-dig
The script is intended for automatic placing of Sell Stop pending orders, Stop Losses and Take Profits on the user specified levels. This script is not that useful as "Virtual pending buy stop", since short positions are opened as Bid price crosses the levels. Thus spread widening is not dangerous. Nevertheless, you need to have this script to prevent unwanted hitting of the Stop Loss levels.
Automation of the process of placing the Sell Stop pending orders, Stop Losses and T
Does not support openning multiple orders on a single symbol on MT5
MultiMTCopier MT5Receiver - new and improved multi-terminal positions copier for your real/demo account, works faster, requires less, flexible in managing and upgrading, new information support. This Expert Advisor is designed for the MetaTrader 5 terminal, trades will be copied into this terminal.
The EA will copy all positions without delays Additionally integrated notification in situations requiring user
Percent Crosshair is a powerful and easy percentage measure tool.
Measure the chart percentage very quick! Don't waste your time anymore!
Just attach the Percent Crosshair indicator in the chart, select crosshair mode at toolbars or press "Ctrl+F" and start using the crosshair as you always do! The percent measure will be next to the indicative price.
Customize your indicator the way you want!
There are 4 entry parameters:
Positive % color: set the desired color when % is positive. Negat
Thanks and Yep, that's the exact help file I referred to that doesn't really seem to say much about ...
conceptual comment on the changes in Mt4 (600+) regarding the OnTick() versus Start() command
Not being sarcastic, I respect you're an accomplished and polished coder, but even with your greater experience, you don't elaborate.
The OnTick help file says... "can now be used instead." (What is OnTick() used instead of) ?
The Tick event is generated only for Expert Advisors, but this does not mean that Expert Advisors required the OnTick() function, since not only NewTick events are generated for Expert Advisors, but also events of Timer, BookEvent and ChartEvent are generated. It must be declared as the void type, with no parameters:
So basically, if I just stick with Start(), declare locals static and continue to use RefreshRates() or MarketInfo() strategically, it's about the same thing? I understood the Start() command was fired with the tick event already and that OnTick() let's any new ticks pass by just like Start() will, if the scan in latent in completion relative to next event.
Is my understanding wrong, or how then does the OnTick() event benefit code or performance, inside the Start() routine otherwise?
What is the distinction, purpose or benefit of OnTick(), especially forced as void? Am I missing some other help file that builds on the concepts?
Does it inform me inside Start() that yet another Tick has occurred while the Start() event was in process, (pseudo critical code section-ish)?
Is it just a matter of equivalency or support for higher order high level code applications, OO, or otherwise?
I tried to emphasize I did the homework to look it up. I just don't see any real information imparted beyond basic construct.
I'd like help on this too, so commenting in the hope that the question gets bumped up the list. I'm afraid that compared to the body of knowledge out there on just about any other language, the documentation and tutorials on MQL4 are just about useless.
I also have found the various references mentioned, and I also have bumped my head on local vs. global variables, so if anyone can make these questions clear I think there will be a lot of pleased new programmers..
I'm not entirely sure what is being asked, but in a nutshell (and with some gross oversimplifications):
Just replace Start() with OnTick()... they are synonymous. Think of it as a terminology change.
Before Build 600+, you were effectively limited to running code once per tick. If a tick didn't come in, the code didn't run.
Now you can run code on a timer using OnTimer(), or when certain events happen like mouse clicks, pressing keys or moving objects using OnChartEvent().
A variable with local scope can only be accessed from within the procedure where it was declared. So if you declare "double myVar" in OnInit(), you can't access "myVar" in OnTick(). Variables with a local scope do not hold their values once the procedure has run, unless they are declared as static e.g. "static double myVar".
A variable with global scope can be accessed from anywhere within the EA. So if you declare "double myVar" at the top of your EA (outside of any procedures), you can access "myVar" in OnInit(), OnTick() or anywhere else you want. Variables with a global scope will hold their values between procedure calls.
A global variable is something different - it can be accessed between different EAs. They are stored for 4 weeks after their last use.
Ok, Thank you. This confirms a better context to it, for those lacking experience in Mt5 as I am...
Possibly my question should have been, "WHY" is OnTick() used instead of Start().
I view your answer to mean the OnTick() handler basically encourages improved Mt5 code structure and performance options in as much as it's requirements on variables, stack, heap, etc. which starts to make some sense in evolution of Mt4 > Mt5 and future code provisions perhaps. Overall, avoiding long or far calls can have a huge cumulative impact on overall performance and integration stability, something which has always been an issue in the MT4 scripting constructs permitting sloppy code design.
It honestly was not clear to me in the support files that OnTick() might not apply inside the Start() cycle in some instances. It helps if considering OnTick() as an explicit option of replacement to Start() as likely the safest way to view it. I didn't test if OnTick() can possibly be permitted inside Start() but it would now seem redundant and prone to several issues if one could even do so, yet there may have been instances beyond obvious for lack of clarification in the help file, leaving assumptions to dangle.
Last, I did not find this, "remained for compatibility" searching help or prior web reference unless you're simply clarifying; all good either way. :)
Since I'm not familiar with Mt5 (which likely doesn't support the Start() command) and my question is here in the Mt4 forum, this also suggests an "Mt4.5" context in compatibility. I also don't use the newer template provisions which I'm sure would be intending to encourage Mt5 migration and a more rigid learning path.
The bottom line appears to identify Mt5 as supporting stateless design I would think points toward Object Oriented methods. These cross compatibilities appear to ease differences for Mt4 coders fumbling up to Mt5 methods and greater concepts of more virtual design versus the "stateful" event trap. The flexibility in Mt5 seems to become nearly endless but perhaps forces a greater reliance on state machine at the designer's hands inside the greater flexibility which might even lend well to UML design and very high-end potential Mt4 has wanted for.
I'm making some reaching assumptions but for those of us grappling with the changes to Mt5 outside of good academic training, making the transition without the benefit of more formal learning is a real pit for wanting to avoid building on poorly written code, if we can understand the newer concepts better. The Mt4.5 after all has become a "forced" initiative by MQ, so those of us not familiar with Mt5 have our hands full keeping forward code maintenance with learning better design integrity nearly overnight. This is where any secondary help file system really cannot provide a novice with much better than we have currently, except by greater discussion and if not for the compatibility of crossover options like OnTick() being permitted along side of Start() in Mt4.5 as a "bridge" to Mt5. It otherwise defines the "leap" to Mt5 which has been thwarting MQ from bringing Mt4 coders forward to Mt5 as they must. Painful as that may be for some of us, the potential benefits outweigh the struggle, if one intends to stay relevant as methods progress.
Owing to the frustration the build 600+ (Mt4.5) migration has been, the initiative MQ has undertaken is one of the most involved I've personally seen in any compiler overhaul and language upgrade. The Mt4.5 stage of this represents a huge afterthought with significant engineering thrust by MQ, still working out bugs even now. I'm sure some if not many might disagree but realistically Mt5 had to mature to a certain point before Mt4 end of life migration could be made a requirement supporting mass transition. Fuller understanding of this need (and the benefit for those of us confronted by new learning) couldn't be more important to help novices understand and justify the need to "just bite the bullet and go back to the work required to learn it" (and risk asking dumb questions in the open like the OnTick() command you've helped clarify).
Not so much a rant, but hopefully to encourage others beyond simply "RTFM" and to realize it is a transitional process not always having obvious context in reference, needing further clarification for those learning.
Thanks once more and feel free to correct my assumptions if appropriate or the thread can end. Simple (or stupid) as it was, you've helped me understand better why the question of OnTick() occurred and why the answers are not always obvious, since the forced migration has literally kept me too busy to learn Mt5 properly, frustrating almost like a paradox. Yes, I should have followed Mt5 sooner, like many. Maybe it helps others now stuck learning in similar ways too. It's a good thing we have those more experienced with patience, willing to help answer the sometimes "less than obvious" dumb questions on the way to Mt5. :)
Not to hijack your thread, but the main reason why nobody cares for MT5 and thus very low adoption was the fact that the language was not backward compatible at all with existing MT4 code. You pretty much had to re-write. Secondly, MT5 enforces the most stupid of rules used in only one country that I am aware of - the no hedging rule. You cannot hedge with MT5. This pretty much broke trading for everybody in the world except those in the US.
And I am not interested in going into a discussion about hedging except to say that I run multiple strategies on the same account. Some longterm, some shortterm. So I must be able to hedge and to control my margin effectively. If I cannot hedge, I need to run multiple accounts and thus require much more capital. Thankfully I am not in the US and will also never use MT5.
Hopefully now that MT5 is being backported to MT4, MT5 will eventually die and they can focus their efforts on a single codebase for a more stable environment.
Added new char, short, long, uchar, ushort, uint, ulong and double
data types. This will allow transferring codes from other C++ like
languages. Data of various types is processed at different rates.
Integer data is the fastest one to be processed. A special co-processor
is used to handle the double-precision data. However, due to the
complexity of the internal representation of floating-point data, it is
processed slower than integer one. Typecasting has also been implemented.
Strings are now presented in
Unicode format, though they were in ANSI format (single byte ones)
before. That should be considered if the program uses DLLs and passes
string variables to them.
variable is now of long type. The time series for accessing the volumes
also consist of long type arrays. It is recommended to use explicit
casting of data having this type to the target type in old MQL4 programs
to avoid type overflow error.
Structures and classes, object pointers, void type and this
key word allowing an object to receive a reference to itself have been
added. All object-oriented programming standards are supported:
ООP allows developing programs
using classes. This facilitates debugging and development of large
applications, as well as provides ability to reuse previously generated
code multiple times due to inheritance. However, that does not mean that
you cannot generate your MQL4 code in procedure-oriented style as
before. You can develop your programs as you did in the past if you
don't need the new features.
init(), deinit() and start() predefined functions have remained for compatibility, however, OnInit(), OnDeinit(), OnStart(), OnCalculate() and OnTick() ones can now be used instead. Besides, new predefined OnTimer(), OnChartEvent() and OnTester()
handler functions have been implemented. In the previous MQL4,
predefined functions could have any parameters and any return type, and
they could be called by their names, not signatures. In the new MQL4,
all predefined functions should strictly correspond to their signatures.
In other words, they should have precisely defined set of parameters
and return type.
WHRoeder 2014.10.16 14:59 #
I gave you the link why couldn't you read it?
Mmmm, apparently because I had already exhausted the local help files in frustration and already moved into the OnTick() help description on that link before I searched for "Compatibility", being over-focused on the single function of interest rather than the overall. I was then AGAIN returning to the same process on your reference and shot past the first link, to the OnTick() reference redundantly, search fail. To that extent the adage RTFM applies toward being more thorough, right? Sorry. (blush) I've spent a lot of time hammering help files and Google in recent weeks which has created a negative habit of glancing into drill down, which in this case worked against the goal. This underscores the extent of frustration of dealing with relatively wide compiler changes amid bringing existing, running code forward in a live setting compounded by the compulsory nature of this transitional Mt4 change. Reminiscent of past Perl updates fighting with backward compatibility. Most of what I'm dealing with are stateful issues of real-time tick mode processing which is a tedious issue typically in playback mode as is, when scope issues begin to show up while trying to improve the application along with updating where possible to better structure.The sun was in my eyes. I had the flu that day. Yeah, that's it. :/ I'm probably not the only one that will benefit from this incursion through this mud puddle having fairly beat this horse to death [SOLVED], so best I can say for my oversight is "Point taken.", Thank you for bringing it home, RTFM THOROUGHLY. :)MTC
Mmmm, apparently because I had already exhausted the local help files in frustration and already moved into the OnTick() help description on that link before I searched for "Compatibility", being over-focused on the single function of interest rather than the overall. I was then AGAIN returning to the same process on your reference and shot past the first link, to the OnTick() reference redundantly, search fail. To that extent the adage RTFM applies toward being more thorough, right? Sorry. (blush) I've spent a lot of time hammering help files and Google in recent weeks which has created a negative habit of glancing into drill down, which in this case worked against the goal. This underscores the extent of frustration of dealing with relatively wide compiler changes amid bringing existing, running code forward in a live setting compounded by the compulsory nature of this transitional Mt4 change. Reminiscent of past Perl updates fighting with backward compatibility. Most of what I'm dealing with are stateful issues of real-time tick mode processing which is a tedious issue typically in playback mode as is, when scope issues begin to show up while trying to improve the application along with updating where possible to better structure.
The sun was in my eyes. I had the flu that day. Yeah, that's it. :/
I'm probably not the only one that will benefit from this incursion through this mud puddle having fairly beat this horse to death [SOLVED], so best I can say for my oversight is "Point taken.", Thank you for bringing it home, RTFM THOROUGHLY. :)