Re: Push to client - Compile options and user actions don't get imported

[j.beckeringh@xxxxxxxxxxxxxxxxxxxxxxxxxx]

Edmund, Eric,

Do you have any idea why the compile commands and the user actions don't 
show up in the new workspace?

Joep Beckeringh 
systeemontwerper 
Pantheon Automatisering B.V. 
Heerenveen 

Postadres 
K.R. Poststraat 101-2 
8441 EN Heerenveen 
T. 0513 657 357 
F. 0513 654 695 

info@xxxxxxxxxxxxxxxxxxxxxxxxxx 
www.pantheon-automatisering.nl 
KvK 01055135 


> Joep Beckeringh <joep.beckeringh@xxxxxxxxxx>
>
> 09-02-2016 14:52
>
> [WDSCI-L] Push to client - Compile options and user actions don't get 
imported
> Last week I was experimenting with Push To Client; I noticed the 
> following strange behaviour:
>
> After I exported my configuration I created a new workspace, 
> connected to the same server, got a prompt to accept the 
> configuration, accepted it and everything I expected to be there was
> there; including a number of added compile options and user actions.
>
> Then I went to a colleagues PC and created a new workspace, 
> connected to the same server and accepted the prompt. After that, 
> the connection and the filters were there, but only the default 
> compile options were there and no user actions. When I go to 'Work 
> with compile commands' I see the (only) filter pool is PTHPC096, 
> which is the name of my PC, where the export file was created.
>
> Then I exported my configuration to a different location, mailed the
> configuration file to my colleague and imported it on his PC. Same 
effect.
> Does anybody else export configurations and if so, do compile 
> commands and user actions come across?
>
> Joep Beckeringh
> Pantheon Automatisering b.v.