Author Topic: Remembering Selections  (Read 1479 times)

Tags:
  • All members
  • Posts: 84
Remembering Selections
« on: 21 Mar 2010, 08:46 »
Hi Oxa,
I use MFPro mainly for Horse races but I think the following would be useful in all markets.

Is it possible to have a drop down box with a list of the selection variables that will be remembered for each selection that a remembering trigger remembers?
This could be next to the remember action box and pop up in a similar way to that for the cancel actions.
This drop down box would have a list of ALL the selection variables that will be remembered (stored in memory) for each matching selection.
At the moment, if your trigger conditions produce a list of 10 Matching Selections then ALL the selection variables are remembered (stored in memory) for ALL 10 JUST IN CASE you MIGHT later want to access any of them.
This process I believe is an inefficient use of computer resources (ram).
Much better to have a drop down list with check boxes next to all the selection variables that will be remembered.
This list will have all the boxes checked (ticked) as default...as is the case at the moment.
However, the user could open this drop down box and "untick" those selection variables they're NOT interested in remembering leaving ticked only the ones their triggers do want/need.

So for example...I only want to remember for future use the back, lay and last traded price of All Matching Selections. I would "untick" all others leaving just those 3 ticked (of what use is the horses saddlecloth number? ... unless you do triggered betting to play lucky numbers!)  ;D
If matching selections=10 that's 30 items of information memorized.
At present MFPro would memorize 1170! (117 selection variables * 10 selections).
...and if you are monitoring more than one market?
Of course any trigger trying to access a variable that was NOT remembered (because it was unticked) would get the usual error or 0 in return.

I believe this procedure would free up valuable ram for other more important stuff.

Can I also suggest you add to the list, of variables that will be rememberd, the state of the market at the time the remembering trigger executes i.e. the market_volume, b_book & l_book so that we can access them with [triggerName]_market_volume or [triggerName]_b_book etc.

While writing...MFPro has maxbp_[minutes] and minbp_[minutes] etc. Can we have a maxlt_[minutes] and minlt_[minutes]? i.e. max/min last traded in the last [minutes].
I find the actual traded price is more indicative of a horses true probability than the back price on offer which can be wishful thinking on the part of the offeror and can be withdrawn without ever being taken/matched.

O
If you lose...don't lose the lesson!

  • All members
  • Posts: 60
Re: Remembering Selections
« Reply #1 on: 21 Mar 2010, 18:40 »
Hi Oxa

Can I offer my support for the above suggestions. As MF Pro gets more complicated - a good thing - use of CPU resources seems to be becoming critical to avoid periods between refreshes that are much longer than the refresh rate that one sets (my hardware is Quad-Core processor with 20MB per sec cable broadband, so should be adequate).

Regards

Ed.

 

Please note, BetFair is seems to be currently OFFLINE