|
| JFOREX-3653 no locked state anymore? |
|
RoadRunner
|
| Post subject: JFOREX-3653 no locked state anymore? |
Post rating: 0
|
Posted: Wed 28 Mar, 2012, 09:21
|
|
User rating: 3
Joined: Wed 18 May, 2011, 16:25
Posts: 331
Location: SwitzerlandSwitzerland
|
Dear Support, Quote: API 2.6.60:
addToMainChartUnlocked(T) - Method in interface com.dukascopy.api.IChart
Deprecated. Please, use method @link IChart.addToMainChart(IChartObject) There is no objects division onto locked and unlocked anymore How can I prevent users from moving certain drawing objects on the chart with the new API? Kind regards, RR.
|
|
|
|
|
 |
|
API Support
|
| Post subject: Re: addToMainChartUnlocked(T) deprecated - no locked state anymore? |
Post rating: 0
|
Posted: Wed 28 Mar, 2012, 12:24
|
|
User rating: ∞
Joined: Fri 31 Aug, 2007, 09:17
Posts: 6139
|
RoadRunner wrote: How can I prevent users from moving certain drawing objects on the chart with the new API? In the current API implementation this is not possible, the functionality will be reintroduced with the JForex-API 2.6.64. Consider a temporary workaround using ChartObjectListener, for instance, on object select, deselect the object, or on object move, move back the object. See example using ChartObjectListener: https://www.dukascopy.com/wiki/#Handle_chart_object_events
|
|
|
|
|
|
|
RoadRunner
|
| Post subject: Re: JFOREX-3653 no locked state anymore? |
Post rating: 0
|
Posted: Thu 29 Mar, 2012, 13:42
|
|
User rating: 3
Joined: Wed 18 May, 2011, 16:25
Posts: 331
Location: SwitzerlandSwitzerland
|
|
ok, thank you for your reply.
We use a lot of visualisation in our backtesting, i.e. include a lot of lines, symbols, etc.
As now all objects are unlocked, they all show up in the chart-object-tree in the desktop's workspace client.
When we do run backtests over longer periods, this adds up to thousands of objects.
I haven't yet tried with the current release, but when you did temporarily remove the lock-feature in an earlier version (about 1.5 years ago?), the backtesting got slowed down so much that the application was stalling because the object tree was permanently updating.
Will you re-introduce the old functionality (addToMainChart and addUnlockedToMainChart) or will you introduce new methods and lock/unlock-features?
I hope you can release 2.6.64 anytime soon?
Kind regards,
RR.
|
|
|
|
|
|
|
API Support
|
| Post subject: Re: JFOREX-3653 no locked state anymore? |
Post rating: 0
|
Posted: Thu 29 Mar, 2012, 13:53
|
|
User rating: ∞
Joined: Fri 31 Aug, 2007, 09:17
Posts: 6139
|
|
We will add such possibility.
|
|
|
|
|
|
|
API Support
|
| Post subject: Re: JFOREX-3653 no locked state anymore? |
Post rating: 0
|
Posted: Fri 30 Mar, 2012, 08:42
|
|
User rating: ∞
Joined: Fri 31 Aug, 2007, 09:17
Posts: 6139
|
|
|
|
|
|
|
API Support
|
| Post subject: Re: JFOREX-3653 no locked state anymore? |
Post rating: 0
|
Posted: Fri 30 Mar, 2012, 17:06
|
|
User rating: ∞
Joined: Fri 31 Aug, 2007, 09:17
Posts: 6139
|
|
Added possibility to lock ChartObjects from strategies. See IChartObject.setLocked(boolean)
It will be available in a next API version.
|
|
|
|
|
|
 
|
Pages: [
1
]
|
|
|
|
|
