Thank you Michaël, I will test that.
Nicolas
On 29 June 2017 at 08:03, Michaël Michaud
wrote:
> Nicolas,
>
> If you want the option to be persistent (saved in the workbench-state.xml
> file), you must use the PersistentBlackboard :
>
> You can get it from the workbench context :
> PersistentBla
Nicolas,
If you want the option to be persistent (saved in the
workbench-state.xml file), you must use the PersistentBlackboard :
You can get it from the workbench context :
PersistentBlackboardPlugIn.get(context.getWorkbenchContext())
or directly form JUMPWorkbench
PersistentBlackboardPlugIn
Hi Michaël,
Yes I can add it.
What would be the best way to get options from Blackboard ?
I see methods to get blackboard from a plugin's context, but for
"standalone" classes, like WMService, it is possible to retrieve to it ?
Thanks,
Nicolas
On 28 June 2017 at 20:50, Michaël Michaud
wrote:
>
Hi Nicolas,
Sure, it makes sense. I was just too lazy to implement it as you describe.
Do you want to add it ?
Ede, any objection ?
Michaël
Le 28/06/2017 à 19:57, Nicolas Ribot a écrit :
Hi,
I saw a recent commit from Michaël concerning WMS timeout.
When developing local web services, I oft
Hi,
I saw a recent commit from Michaël concerning WMS timeout.
When developing local web services, I often need a bigger timeout (for
instance when displaying a zoom level > 16 on a big area).
Would it make sens to add parameter options to set timeout values, for
instance in the Network tab ? :
