FVOE - FxCraft Visual Order Editor (LVOE) | Forex Factory

Options

Go to
Permalinks
Print Thread

Similar Threads

Luktom visual order editor TSL Bug 32 replies

Help with Visual Order Editor 44 replies

LUKTOM visual order editor unusable since 8/5 update of MT4 2 replies

Visual order editor expert - bug 4 replies

Adding Features to Visual Order Editor 0 replies

Attachments: FVOE - FxCraft Visual Order Editor (LVOE)
Exit Attachments

FVOE - FxCraft Visual Order Editor (LVOE)

  • #1
  • First Post: May 20, 2013 9:01am May 20, 2013 9:01am
FVOE - FxCraft Visual Order Editor (old LVOE) is well known, easy and intuitive position management.

We start this thread to improve communication with users and what goes after that: improve FVOE.

I encourage to ask questions about FVOE: how it works, what is in it, what can be add to it, and others.

(as a commercial member we can’t write in threads like: http://www.forexfactory.com/showthread.php?t=330076 so please ask question about FVOE here).


With concrete orders / plan of modifications please write to:

[email protected]

and we discuss details.






1.

New version is available 1.6.3 on our site:

http://fxcraft.biz/en/product/fxcraf...-order-editor/

(fixed bug with flashing pending order lines).


From version 1.6.2, when paremeter [showOLforOpenOrders] is set true, FVOE shows open level line also for open orders.

This is a significant change if we want to use FVOE on the new version MetaTrader 4, so as not to collide with the new features on the platform.

Please turn off in MT4: tools -> options -> charts -> show trade levels

Then when you set the [showOLforOpenOrders] = true, and set in the chart options “show object descriptions” everything will work as before.



2.

about close part lines

Quoting Rivabex
I use the Ivoe1.6.1 Version of the EA . Is it possible to change the ClosePart Level to be below the current price on Buy trade and Above current price for a Sell trade on chart , ie : Like a ClosePart SL level.

in basic version it is impossible but of course we can modify it for You.
  • #2
  • Edited 12:37pm May 21, 2013 12:12pm | Edited 12:37pm
Hello

why if i open 2 buy order , and only after i start EA fvoe 1.6.3 at the second TP i got error message in oanda "tradexxxxxxx could not be closed due to fifo violation" .... is it normal ?
  • #3
  • Edited 5:06pm May 21, 2013 3:59pm | Edited 5:06pm
Quoting Redsunfx
Hello why if i open 2 buy order , and only after i start EA fvoe 1.6.3 at the second TP i got error message in oanda "tradexxxxxxx could not be closed due to fifo violation" .... is it normal ?
It usually means you have another chart open for the same pair, and there are open trades on that chart which are older than the trades you are currently trying to close on this new chart with the EA. Since you are subjected to the NFA FIFO rules, maybe avoid trading more than one chart for the same pair (you can have multiple chart views of course), because the oldest trade must be closed first according to FIFO.

Google for "trade could not be closed due to FIFO violation". It's only applicable to US clients and brokers under CFTC/NFA regulation.

LVOE (now FVOE) works well with multiple positions and closing partials on each position.
Attached Image (click to enlarge)
Click to Enlarge Name: au.png Size: 45 KB
No longer trading forex. Looking for full time job.
  • #4
  • May 23, 2013 9:35am May 23, 2013 9:35am
mmaker

which version are you using ?
  • #5
  • Jun 19, 2013 1:58am Jun 19, 2013 1:58am
Thank you for version 1.6.3 and the manual. I have a couple of questions please.

When I run compile there are 2 warnings. These are:

  1. 'oType' - comparison expression expected Crogram Files (x86)MetaTrader - AxiTraderexpertsfvoe 1.6.3.mq4 (117, 16)
  2. 'oType' - comparison expression expected Crogram Files (x86)MetaTrader - AxiTraderexpertsfvoe 1.6.3.mq4 (152, 22)

These look like typos. Do you have a correction?

I discovered that the application does not detect and adjust for 4 or 5 digit brokers. This was a surprise and produced an amusing set of orders!

Do you intend to release a version that adjusts for digit size?

Take 2 aspirin and call me in the morning!
  • #6
  • Jun 20, 2013 4:49am Jun 20, 2013 4:49am
Quoting Pjt
Thank you for version 1.6.3 and the manual. I have a couple of questions please. When I run compile there are 2 warnings. These are: 'oType' - comparison expression expected Crogram Files (x86)MetaTrader - AxiTraderexpertsfvoe 1.6.3.mq4 (117, 16) 'oType' - comparison expression expected Crogram Files (x86)MetaTrader - AxiTraderexpertsfvoe 1.6.3.mq4 (152, 22)These look like typos.
if( X ) is equivalent to if( X != 0)

so we have:

if( oType == 1 || oType == 3 || oType == 5 ) <=> if( oType % 2 != 0) <=> if( oType % 2 )

it's shorter and faster, and this warning is compiler's overreaction.


Quoting Pjt
I discovered that the application does not detect and adjust for 4 or 5 digit brokers. This was a surprise and produced an amusing set of orders! Do you intend to release a version that adjusts for digit size?
its hard to create universal digit detection (for 5/3, 4/2 and stocks) so best solution is parameters in points and conscious investor.
  • #7
  • Jun 20, 2013 5:01am Jun 20, 2013 5:01am
OK, thanks for the response.

I thought the EA was only for MT4. I'm only aware of 4 and 5 digit brokers so I guess that universe is only 2 and hence not so hard really. However, not to worry, as you suggest, one need only know how many apply and either add a digit (5 digit brokers) or not (4 digit brokers).

Cheers
Take 2 aspirin and call me in the morning!
  • #8
  • Sep 27, 2013 12:51pm Sep 27, 2013 12:51pm
Is there away to change properties once it is allready open? F7 wont work, neither the menu option.

If I decideto change TP percentanges or something.
Thoughts are things
  • #9
  • Sep 27, 2013 1:21pm Sep 27, 2013 1:21pm
If you set parameter use_timer on true you cannot change parameters, otherwise it is possible.
  • #10
  • Sep 28, 2013 2:13pm Sep 28, 2013 2:13pm
Quoting FxCraft
If you set parameter use_timer on true you cannot change parameters, otherwise it is possible.
What is the advantage or disadvantage of using either settings? use_timer is by default set to asynchronous (true), but if I set to synchronous (false) in order to move the lines would there be adverse effects?
No longer trading forex. Looking for full time job.
  • #11
  • Sep 28, 2013 3:23pm Sep 28, 2013 3:23pm
If you set use_Timer on true and move lines (e.g of stop loss, take profit) order will be modified immediately. If use_Timer is set on false order will be modified on another tick. So, the first option is faster than.
  • #12
  • Sep 30, 2013 7:39am Sep 30, 2013 7:39am
Thank you.

Today I'venoticed the EA didnt set to BE or close partialy.
I've set it to close 33% of 0.03 lot. Is this allrigt?
Does the EA work with micro lots?

Maybe the spread is an issue, but it was 1.3 pips over the line and spread is almost always between 0.3 and 0.5 pips.
Attached Image (click to enlarge)
Click to Enlarge Name: 1.jpg Size: 255 KB
Thoughts are things
  • #13
  • Oct 2, 2013 3:04am Oct 2, 2013 3:04am
Hi Quezoy,
can you tell me values of the following parametrs? use_cp, cp_size_or_percent, cp_levels, cp_lots, cp_color, cp_style?
  • #14
  • Oct 4, 2013 5:09am Oct 4, 2013 5:09am
use_cp true
cp_size_or_percent false
cp_levels 500
cp_lots 33
cp_color royalblue
cp_style 1
Thoughts are things
  • #15
  • Oct 4, 2013 6:58am Oct 4, 2013 6:58am
I checked your settings on a demo account and it closed a position. So the only option is that spread was big and that's why the position was not closed partially and it break even did not work.
  • #16
  • Oct 9, 2013 3:46pm Oct 9, 2013 3:46pm
I wanted to let u know that it works well now. Was probably the spread.
Thoughts are things
  • #17
  • Feb 6, 2014 5:45pm Feb 6, 2014 5:45pm
Genius bit of code!

Can you use the break even and trailing stop loss together?
e.g. SL is 50 pips, and initial target is 50 pips. When price reaches 50 pips, move stop loss to BE+20 say (offset 20) and then trail price movement by 30?

The reason for doing this is so that trailing stops only start once price has moved X pips away from entry.
  • #18
  • Feb 6, 2014 11:00pm Feb 6, 2014 11:00pm
Quoting unclezoot
Genius bit of code! Can you use the break even and trailing stop loss together? e.g. SL is 50 pips, and initial target is 50 pips. When price reaches 50 pips, move stop loss to BE+20 say (offset 20) and then trail price movement by 30? The reason for doing this is so that trailing stops only start once price has moved X pips away from entry.
I did something similar, but created two separate scripts instead.

FVOE_1 : SL at 50 pips, Take Profit at 50 pips for 50% position. No BE Stop. No Trailing Stop.
FVOE_2 : SL at 50 pips, Take Profit at 100 pips for 50% position. Move Stop Loss to BE+20 after 50 pips. Trailing Stop at 30 pips.

So after you placed your entry for 2 lots (or any even multiples), you drag-and-drop FVOE_1 into the chart window and it will set Stop Loss at 50 pips and first take profit at 50 pips. When price reaches and exceeded 50 pips, it would exit 50% position. Now you manually drag-and-drop FVOE_2 into the chart window, it will target 100 pips for the remaining 50% position while trailing 30 pips.

See if that works for you. It's like semi-automatic.
No longer trading forex. Looking for full time job.
  • #19
  • Sep 17, 2014 1:31pm Sep 17, 2014 1:31pm
Hi,

I attached 1.6.3 to a DAX30 chart and the problem here is with the increment of 0.5.

So if I drag the line to e.g. 6702.4, the line will sit there but the according SL does not change as this is not a valid value. Valid values can only be .0 or .5

Can I make the expert to round up or round down to what is closer? If I show the trade lines in MT4 and move them around, they will attach to only valid values.

Thanks for info,
  • #20
  • Sep 22, 2014 12:40pm Sep 22, 2014 12:40pm
Dear Frenchie,
now it is not possible. However, we can modify our product , so it will satisfy your needs. Please, visit our website (it is in our profile) and contact us via mail.
0 traders viewing now