stoyan's dashboard

stoyan marked one of Antonin Hildebrand's replies in BinaryAge as useful. Antonin Hildebrand replied to the problem "Slowness working with very large javascript files".

stoyan replied on July 15, 2008 12:07 to the question "Stop writing to the registry" in BinaryAge:

Don't get me wrong I happily watch the refresh counter. And I'll miss it if you remove it, but just don't think it should be stored in the registry. I'm not talking about removing it I'm talking about moving it off the registry. I'm sure you have considered a XML store for projects (settings.xml) just for make them more easily for backing. This is also the case for the refresh counter. I don't really know the backgrounds of this particular decision you have made. May be it is too expensive to you to write to a file every time refresh occur.

stoyan replied on July 15, 2008 11:53 to the idea "Introduce logging for debug purposes" in BinaryAge:

Only once (actually few other times but with the same trace info) and the report was incomplete. I had reported that in
http://getsatisfaction.com/xrefresh/t... - but is it somehow x64 related. Just to keep thinks clear, yes I'm talking about the tray client.

stoyan asked a question in BinaryAge on July 14, 2008 16:32:

Stop writing to the registry

Is it possible to stop writing those values in registry. I'm talking about the refresh counter and the others? I personally don't want those info written in the registry.

stoyan shared an idea in BinaryAge on July 14, 2008 16:25:

Introduce logging for debug purposes

It'll be very good for debugging purposes if you introduce a debug log (brief and verbose) since I get random crashes (on Win XP x32 and x64) at least once a day without the build-in crash reporting system to react in any way. The logged info will be very valuable for tracking down the problem(s).

stoyan reported a problem in BinaryAge on July 03, 2008 21:42:

Manual editing of the Path leads to crash

This is 100% reproducible.
When manually editing the Path in the configuration window after first typed character or arrow key pressed (to move the cursor left or right) XRefresh crashes showing the "Oooops!" dialog. Since the trace is incomplete I'll post it here.

at XPTable.Editors.KeyMessageFilter.PreFilterMessage(Message

That's all of it.

stoyan started following the problem "Refresh only tabs containing documents from the monitored folders" in BinaryAge.

stoyan replied on July 03, 2008 21:29 to the problem "Refresh only tabs containing documents from the monitored folders" in BinaryAge:

Here is my point of view on this subject. There are at least three ways to accomplish this task. It is true - I don't even know how implementable they are, but that soon will be clear (:
1. to require one more field in configuration dialog: URL (or part of) that will be matched to reveal the tab to be refreshed;
2. same as 1 but for page title;
3. from tab context menu to choose which tab to refresh, if there aren't any chosen tabs refresh them all!
My pick is for the third one with just one condition to use *only* the tab context menu since it is *tab related* action.

stoyan reported a problem in BinaryAge on June 26, 2008 06:04:

XRefresh crash under Windows XP x64

XRefresh crashes under WinXPx64 while choosing project type. The type menu shows only the first item and XRefresh closes w/o any error. Doesn't seems to has anything to do with the Fx setup since there's no matter if Fx is running or not.