Hi,
I'm running two instances of FME on the same machine, one 64 bit (running with a long-running job), and one 32 bit running a small job.
Whenever I enable "full inspection" in the 32 bit instance, the 64 bit instance immediatedly responds by turning full inspection on here as well, at least visually.
Is there a "leakage" of settings between multiple instances of FME, even across the 32/64 divide ?
Is this "leakage" real, or just an unwarranted display issue ?
Cheers
Lars I.
Hi Lars
I think this is the intended behaviour. Settings at that level are stored in the registry, not in the workspace. That way when you close or reopen Workbench the setup is the same as it was before - for example all windows are in the same location - regardless of the workspace you opened. And that's a good thing.
When you have different instances of FME I suspect they use the same registry settings to store that information. That way if I install a new FME the setup is exactly the same as the one I left. Again, that's a good thing... unless you have two FME's open at once.
And this particular setting is perhaps more visible than others.
So I could file this with our developers but I don't think it would get changed. I think they would say the amount of work (I think it would be a lot) is not worth the result. I can see how it is worse if you use one FME for development and another for production, but I don't know if that's a common scenario.
What I suggest is that you file this as an idea on this site and see if other users agree by voting for it. That way we have evidence that it's something worth spending time on.
Hope this helps explain - even if I can't really provide a fix
Mark
ps - In case you were wondering, I think the key for this is: HKEY_CURRENT_USER\\Software\\Safe Software Inc.\\FME Workbench\\Settings\\Full Inspection Mode
Thanks Mark.
So what you're saying, is that not only do instances overwrite each other's settings, they continuously pull for any changes as well ?
I did see the instance running a workspace react promptly to me changing "full inspection" on and off in the other instance.
I'm fine with multiple instances reading and writing registry values when starting and exiting, this is how other applications work too, but changing state in mid-process seems a little unnecessary and problematic to me.
It would be nice if a running instance wasn't interupted by such changes.
Cheers
Lars
Thanks Mark.
So what you're saying, is that not only do instances overwrite each other's settings, they continuously pull for any changes as well ?
I did see the instance running a workspace react promptly to me changing "full inspection" on and off in the other instance.
I'm fine with multiple instances reading and writing registry values when starting and exiting, this is how other applications work too, but changing state in mid-process seems a little unnecessary and problematic to me.
It would be nice if a running instance wasn't interupted by such changes.
Cheers
Lars
Thanks Mark.
So what you're saying, is that not only do instances overwrite each other's settings, they continuously pull for any changes as well ?
I did see the instance running a workspace react promptly to me changing "full inspection" on and off in the other instance.
I'm fine with multiple instances reading and writing registry values when starting and exiting, this is how other applications work too, but changing state in mid-process seems a little unnecessary and problematic to me.
It would be nice if a running instance wasn't interupted by such changes.
Cheers
Lars
Thanks Mark.
So what you're saying, is that not only do instances overwrite each other's settings, they continuously pull for any changes as well ?
I did see the instance running a workspace react promptly to me changing "full inspection" on and off in the other instance.
I'm fine with multiple instances reading and writing registry values when starting and exiting, this is how other applications work too, but changing state in mid-process seems a little unnecessary and problematic to me.
It would be nice if a running instance wasn't interupted by such changes.
Cheers
Lars
On additional idea (and I'm sorry again that it comes to this) is just to run the long - running job from the command line. In the log window, the command line is always there at the top. So instead of running the long job from WOrkbench, use a Command Prompt. OR...you can also run a workspace from the Quick Translator. Either of those places will be immune from runtime workbench settings changes.