AW: new conflict callback API

Hi, Stefan, Von: Stefan Sperling [s...@elego.de] On Wed, May 16, 2012 at 02:52:46PM +, Markus Schaber wrote: >> Hmm, this may lead to _very_ special strategies implemented in the core. >> >> Like when a CoDeSys Device plugged into a Slot conflicts, and a neighbor >> slot is empty. >> >> On t

AW: new conflict callback API

Hi, Stefan, Von: Stefan Sperling [mailto:s...@elego.de] > > On Wed, May 16, 2012 at 02:52:06PM +0100, Julian Foad wrote: > > OK, I appreciate that issue. I see two ways the client lib can help: > > > > 1. providing a set of client-lib APIs to perform the most commonly > > wanted resolutions; > >

AW: new conflict callback API

Hi, Von: Julian Foad [mailto:julianf...@btopenworld.com] > Stefan Sperling wrote: > > Bert Huijben wrote: > > So you mean that instead of calling into a GUI client via a set of > > callbacks, the client library should provide several API functions > > that GUI clients can use to gather conflict in