More suggestions

[NewsArchive]

Id like to renew my call for a filter capability like SB4 had on the upper
file list:) Specifically, the ability to filter out some extensions, as
well as just display exe and dll files etc like in SB4. A folder with
thousands of files in it can be pretty unwieldy and often times you are not
able to make a change to clean it up (like a diff folder for clw files, ico
files etc) because it isnt your code/dev setup.

If it is possible to scan dll and exe files to see if they are in clarion
debug mode, that could save a developer some time on large apps - and some
space in their install, not to mention spurious assert messages that they
may not want users to experience. I wouldnt do this for every install, Im
sure itll be time consuming, but a menu item to invoke would be nice. If
its fast, then doing it automatically would be great:) You could simply
mark the files in the installed file dialog (lower right) with a * or a
different color or whatever.
--

Mark

[NewsArchive]

Mark,

> Id like to renew my call for a filter capability like SB4 had on the upper
> file list:) Specifically, the ability to filter out some extensions, as
> well as just display exe and dll files etc like in SB4. A folder with
> thousands of files in it can be pretty unwieldy and often times you are
> not able to make a change to clean it up (like a diff folder for clw
> files, ico files etc) because it isnt your code/dev setup.

This function will be back soon, thank you.

> If it is possible to scan dll and exe files to see if they are in clarion
> debug mode, that could save a developer some time on large apps - and some
> space in their install, not to mention spurious assert messages that they
> may not want users to experience. I wouldnt do this for every install, Im
> sure itll be time consuming, but a menu item to invoke would be nice. If
> its fast, then doing it automatically would be great:) You could simply
> mark the files in the installed file dialog (lower right) with a * or a
> different color or whatever.

I think our compiler is smart enough to detect a debug EXE/DLL. What about
an (optional) compiler switch so the compiler displays a warning if a debug
DLL/EXE is used?

Thank you for your suggestions!

Friedrich

--
Friedrich Linder
CEO, Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 5

[NewsArchive]

> I think our compiler is smart enough to detect a debug EXE/DLL. What
> about (optional) compiler switch so the compiler displays a warning if a
> debug DLL/EXE is used?

That would be great. I'm sure you can open a DLL and search something to
know this quickly.

Shouldn't need a switch - just in the report, in RED, put up a message
"Warning: xxxxxxx.DLL was compiled in debug mode."

Would this pertain to all languages or just Clarion?

-Robert

[NewsArchive]

Hi Robert,

I think it works with all programming languages (32- and 64-bit files).
I have tested this with Clarion 6.2 EXEs/DLLs and VS2005 EXEs/DLLs
(32-/64-bit) and it seems to work fine.

The new SB5 build is already code complete (will be available tomorrow).
So this "compiler feature" will make it into the next build.

Thanks,
Friedrich

--
Friedrich Linder
CEO, Lindersoft
www.lindersoft.com
+1.954.252.3910

"point. click. ship" - that's SetupBuilder 5

[NewsArchive]

> This function will be back soon, thank you.

Excellent, thanks!

> I think our compiler is smart enough to detect a debug EXE/DLL. What about
> an (optional) compiler switch so the compiler displays a warning if a debug
> DLL/EXE is used?

That works for me. Appreciate it:)

--

Mark