Next version of Tincr coming soon.

[Ryan Ackley]

Currently evaluating the scope of the next version of Tincr. These are the major bugs on my radar

• Losing configurations when the devtools are attached to the inspected window
• infinite auto-refresh cycle for some people
• Memory leak in the NPAPI plugin
• 64-bit ubuntu browse button not working

What did I miss?

I'm also curious who has tried Chrome Workspaces and do you still see a place for Tincr in the future?  

[Alex Giannis]

I would like to add.

• Leaving empty lines in css files
• Changes are not saved with Auto Refresh enabled   

I have tried Chrome Workspaces on Canary and I was very disapointed. It has a lot of bugs and needs pointless  configurations.

I prefer using Tincr with all the above bugs.

Feature proposal :

It will be great to control the file types are refreshed/changed. For example If you want only to save css changes and leave the other types (html,js) unaffected.In the current version you need to disable the files manually one by one and if a page has many resources  this takes time.

[Mihai Vilcu]

The browse button problem is also present on windows 7 x64 so if you get the chance have a look on that too please.

On Saturday, July 13, 2013 6:41:01 PM UTC+3, Ryan Ackley wrote: