folders and workflows

[taner]

Hi Steinar,

I experienced some issues when working with folders and workflows.

When I'm in FFAStrans and click on my folders, try to rename them or something else the elements behind FFAStrans on the desktop (shortcuts, opened explorer-windows etc) "shine" through FFAStrans, try to come in the foreground, and stop my action. They disappear when I click again in FFAStrans.
This happens always as long as there are elements behind FFAStrans.

When I rename a folder it gets renamed but I often get a second blank folder which has the old folder-name.

When I make template-workflows, duplicate them and move the duplicates to another folder, quit FFAStrans and open it again sometimes the duplicated workflows have the old name again and are located in the original template-folder. This happens sometimes with folders too.

When I make a change on folder-names or workflow-names or move workflows from one folder into another the other machines where FFAStrans is running do not always take over this Change instantly. I have to restart FFAStrans on that machines.

Sometimes I get corrupted folders/workflows (I'm not sure why, maybe because of the issues above). In this case I can't create or move any workflow in this folder but can rename the folder. But always I can't delete the folder through FFAStrans. In this case I have to quit FFAStrans and manually delete the INI-file(s).

Hope that was not too much.

All this issues happens regardless whether I have just 1,2 folders/workflows or 24 folders and 80 wokflows at the moment.

We are working with Windows 7 Professional 64bit Service Pack 1.

Edit: it does not happen with Windows 10 Enterprise 64bit. Checked it on my office-Computer. I think I've read in another post of of you that you programmed FFAStrans on Windows 10.

Best

Taner

[admin]

It was not too much but is was a lot But you warned me about that so it ok Reporting bugs is important. More important, they need to be fixed. That's sometimes a lot of work.

First about the "transparent" FFAStrans gui. I have seen this happening but more on Win7 than Win8 and WIn10. FFAStrans use windows api to draw the gui so there are apparently some internal system difference between win7 and win8/10. This is espesially tru when using the gui through RDP on a remote computer. Win7 is darn slow and win8/10 gives much smoother operation. However, because I have seen it myself I'm trying to figure out whats wrong but because it's not critical it does not have my full attention at the moment.

For the inconsistant workflow operations it seems you have som corrupt workflows that makes it all behave weird. I'm not sayint there is no bug but there might be that your workflows triggers some bad code. I'll try an look into it.

-steinar

[taner]

Hi Steinar,

Thanks for response. Yes, you're right. On Windows 10 it is smoother. As soon as I have more time I will create new workflows from the scratch.

Best

Taner