Cannot save changes

[NewsArchive]

Friedrich,

Some new behavior in 7.7.3648.

I had to edit about 10 different scripts (part of my overall
installation). Just fixing one line in each and I press the save button
before compiling.

Some of these scripts gave an error that it could not save the changes
and offered to try again. Choosing the try again option, the changes
were saved. In two cases, it took several attempts.

I did save all the edits OK, so this is a very minor issue. Perhaps the
prior script was still loaded in memory?

I did not close the scripts I compiled, I opened the next one I wanted
to work on thinking the prior script would close. I think the steps to
replicate is like this:

1) Open a script and make a change (like comment in/out).
2) Press save.
3) Compile.
4) Open a different script using the extended pick list or open dialog.
5) Steps 1-4 again.

May take doing the above about 3-5 times before this happens and all my
scripts are on my local C: drive. Win 7 Pro, non-VM.

PS - minor cosmetic issue that has been around a long time - often after
compiling, the toolbar becomes "darkened". Hovering the mouse over the
toolbar makes all the buttons visible again, but the toolbar keeps it
dark color.
--

Russ Eggen
RADFusion International, LLC

[NewsArchive]

Hi Russ,

> Some of these scripts gave an error that it could not save the changes and
> offered to try again. Choosing the try again option, the changes were
> saved. In two cases, it took several attempts.

That means your last virus definition update (or your virus application
update) introduced a bug! Your protection software "locks" the project
file. The SetupBuilder IDE detects this locked file scenario and offers a
retry.

> PS - minor cosmetic issue that has been around a long time - often after
> compiling, the toolbar becomes "darkened". Hovering the mouse over the
> toolbar makes all the buttons visible again, but the toolbar keeps it dark
> color.

Unfortunately, this is completely out of our control. The toolbar is a
standard Clarion window.

Friedrich

[NewsArchive]

BTW, in the past (without the locked file detection) this bug in the
protection software caused data loss. I would suggest to report it to your
anti-virus vendor so they can fix it in the next update!

* SetupBuilder 7.3 Build 3195 (January 07, 2011)

CHANGE : IDE: Minor modifications to the internal SaveScript function
to try to detect "overprotective" protection software product
issues (e.g. "Trend Antivirus" or "NOD32" on Windows 7).

---

* SetupBuilder 7.1 Build 2860 (February 02, 2010)

CHANGE : IDE: Minor modifications to the internal SaveScript function
to detect "overprotective" protection software product issues
(e.g. "Trend Antivirus" on Windows 7).


Friedrich

[NewsArchive]

Appreciate the data! I've added an exclusion for .sb7 files. I'll
report the bug to ESET too.

> Hi Russ,
>
>> Some of these scripts gave an error that it could not save the changes and
>> offered to try again. Choosing the try again option, the changes were
>> saved. In two cases, it took several attempts.
>
> That means your last virus definition update (or your virus application
> update) introduced a bug! Your protection software "locks" the project
> file. The SetupBuilder IDE detects this locked file scenario and offers a
> retry.
>
--

Russ Eggen
RADFusion International, LLC

[NewsArchive]

Wonder if the latest internal builds address this? No big deal as the
functions are still there.

>
>> PS - minor cosmetic issue that has been around a long time - often after
>> compiling, the toolbar becomes "darkened". Hovering the mouse over the
>> toolbar makes all the buttons visible again, but the toolbar keeps it dark
>> color.
>
> Unfortunately, this is completely out of our control. The toolbar is a
> standard Clarion window.
>
> Friedrich
>
>
>

--

Russ Eggen
RADFusion International, LLC