[BR_forum] MyEditBR v3.1.0.3300 Released

Discussion about software products provided for the BR community and created by its members. This includes (but is not limited to): MyEdit, File IO, Screen IO, FNSnap, and Utilities written in other languages for use with Business Rules.

Moderators: Susan Smith, admin, Gabriel

rmills

[BR_forum] MyEditBR v3.1.0.3300 Released

Postby rmills » Mon Jun 01, 2009 9:33 am

Good Morning,

I've released a new version of MyEditBR.

For those who have the support licenses and a recent version of
MyEditBR.exe installed you should be able to use the help menu item "Check
for Updates..." to get the latest release.

Or is you prefer to install a clean copy you can download a new installer
from my website: http://www.mills-enterprise.ca

This version is the first to have direct support for BRv4.2 and some of
the new features found in that release version.

Normally I have a list of new features and bug fixes that I provide in
these announcements, but I forgot my list at home this morning. So I'll
try and provide a list from memory. So forgive me if I miss anything.

New features:

* MyEditBR Debugger Breakpoints

While this feature is not new in and of itself, the debugger
breakpoints have been greatly expanded to provide greater flexability.

New support has been added in MyEditBR to provide better support for
existing BR functionality.

MyEditBR now supports the following break point types:
+ Variable
+ Function
+ Program
+ Line Numbers

Valid support license holders also have new breakpoint functionality as
well. In addition to conditional breakpoint testing there is now a
feature call Pass Counts. The way that Pass Counts work is that if you
set any kind of breakpoint (Var, FN, Program, Line #) and then set a Pass
Count of 5 then the breakpoint doesn't actually happen in MyEditBR until
MyEditBR has detected that the break point position has been passed 5
times.

The Pass Count condition is faster that the Conditional check in that
MyEditBR doesn't have to have a conversation with BR to see if it's time
to return control to the debugger and user. Pass Counts and the
Conditional checks can also be combined to work in tandem. The way that
this works is that you specify a valid break point, a break point
Conditional test and a Pass Count number then run the application. The
MyEditBR debugger then waits until the Pass Count has been triggered
before starting to test the Conditional check. Once both have been
satisfied then the Breakpoint occurs and control is returned to the
Debugger and programmer.

* Debugger Log Messages (BRv4.2+)

MyEditBR has, for a long time had, a messages tool window that for most
people probably did nothing. That has now changed. With the latest
version of BR support for Message logging has been added to BR in the form
of a new built in function:

debug_str(LogLevel:integer; Message:string)

This function can be used where ever you want in any program to provide
logging type of functionality for debugging purposes. It works on a
couple of different levels. If you have no debugger running against a
program, ie your customer is running the application, then depending on
your chosen logging command in the wbconfig.sys file only certain
messages that corresponds to the loglevel number will be logged. If
logging is turned off completely then no messages are logged at all. It
simply becomes a silent function call that does nothing.

If you have a debugger running against the program, the log messages
get sent directly to the debugger and show up on the Debugger tab of the
Messages tool window. BR will also send messages to the window, mostly
they will be BR debugging messages.

MyEditBR provides the means necessary to ignore all logging messages to
to log messages up to certain log levels. The higher the log level the
less important the message is deemed to be, as far as BR is concerned. BR
has specified that they use log level messages from 0 to 10.
MyEditBR allows you to filter messages from 0 to 10. While any number can
be used for a log level, if you want your messages to show up in MyEditBRs
Messages window, it must be log level 10 or less.

If you have BRSupport installed and running you can now see log messages
from it as well.

The configuration setting for both of these can be found on the Options
dialog under Debugger and BR Support respectively.

* Show Same Items

Now for those who don't know me, I'm all for taking a feature from
another project/product and trying to re-implement it in MyEditBR. Show
Same Items is one of those features and it currently only works for BR
source files. There is a new tool bar button that when pressed turns the
feature on. When on, as you cursor through your source code it will
highlight all instances of a token (ie variable) visible on the screen.

So for example if you have this feature enabled and you place your
cursor on the variable VAR1$ then every VAR1$ on the screen will become
highlighted. The colors are set in the Editor Options dialog for the
Business Rules color definitions. (*NOTE*: You may want to configure the
colors before trying to use this feature)

* Expanded Messages tool window

The newly expanded Messages tool window has tabs for the following
message types:

+ Plugins
+ System (MyEditBR)
+ BR Support
+ Debugger

* New Automatic Updating (v3 of the AutoUpdater)

The new automatic updating now allows for Multiple files to be updated
as well as providing information about each file. The update
information messages will now appear on the system tab of the messages
window. This is better than the older update system (v2) in that the
old system only could update the actual .EXE and nothing else.

* New Hints, Warnings and Errors
- 2000 character line limit. (BR v4.2+)
- FNKEY keyword has been deprecated (BR v4.2+)

Bugs Fixed:

- REM comment causing an orphaned line error message
- Additional $ appearing from the code completion wizard when used to
complete a $ terminated token.
- BR Support has been updated to v4.2+

I've fixed a number of other ones as well, but like I said I don't have
all of my information available to me this morning so I can't provide
more than that.

Known Bugs:

There are still a couple of known issues, but I wanted to get this
version released now instead of waiting for them to be fixed. Here is
the list of current known bugs:

- BR Load source from file
and
- Compile BR source to file:

This has been broken somehow, I think it has to do with the new version
of BRSupport that I use (BRv4.2). I'm working with Dan to try and
figure out whether it is something I've done (most likely) or something
to do with the new version of BR. This is currenly borked, so please
don't play with it.

If you have any problems please let me know, I would prefer to have bugs
registered on the support forums (http://support.mills-enterprise.ca)
but will accept br-forum messages as well as personal emails.

Thanks,

Ryan Mills
Mills Enterprise Ltd.





_______________________________________________
BR_forum mailing list
BR_forum@ads.net
http://ads.net/mailman/listinfo/br_forum_ads.net

John
Posts: 507
Joined: Sun Apr 26, 2009 8:27 am
Location: West Orange, NJ
Contact:

[BR_forum] MyEditBR v3.1.0.3300 Released

Postby John » Tue Jun 02, 2009 10:13 am

Isn't there a setting to tell it not to prompt for save on exit? I thought
there was but I'm having difficulty finding it now.

-----Original Message-----
From: br_forum-bounces@ads.net [mailto:br_forum-bounces@ads.net] On Behalf Of
rmills@mills-enterprise.ca
Sent: Monday, June 01, 2009 11:33 AM
To: Business Rules Forum
Subject: [BR_forum] MyEditBR v3.1.0.3300 Released

Good Morning,

I've released a new version of MyEditBR.

For those who have the support licenses and a recent version of
MyEditBR.exe installed you should be able to use the help menu item "Check
for Updates..." to get the latest release.

Or is you prefer to install a clean copy you can download a new installer
from my website: http://www.mills-enterprise.ca

This version is the first to have direct support for BRv4.2 and some of
the new features found in that release version.

Normally I have a list of new features and bug fixes that I provide in
these announcements, but I forgot my list at home this morning. So I'll
try and provide a list from memory. So forgive me if I miss anything.

New features:

* MyEditBR Debugger Breakpoints

While this feature is not new in and of itself, the debugger
breakpoints have been greatly expanded to provide greater flexability.

New support has been added in MyEditBR to provide better support for
existing BR functionality.

MyEditBR now supports the following break point types:
+ Variable
+ Function
+ Program
+ Line Numbers

Valid support license holders also have new breakpoint functionality as
well. In addition to conditional breakpoint testing there is now a
feature call Pass Counts. The way that Pass Counts work is that if you
set any kind of breakpoint (Var, FN, Program, Line #) and then set a Pass
Count of 5 then the breakpoint doesn't actually happen in MyEditBR until
MyEditBR has detected that the break point position has been passed 5
times.

The Pass Count condition is faster that the Conditional check in that
MyEditBR doesn't have to have a conversation with BR to see if it's time
to return control to the debugger and user. Pass Counts and the
Conditional checks can also be combined to work in tandem. The way that
this works is that you specify a valid break point, a break point
Conditional test and a Pass Count number then run the application. The
MyEditBR debugger then waits until the Pass Count has been triggered
before starting to test the Conditional check. Once both have been
satisfied then the Breakpoint occurs and control is returned to the
Debugger and programmer.

* Debugger Log Messages (BRv4.2+)

MyEditBR has, for a long time had, a messages tool window that for most
people probably did nothing. That has now changed. With the latest
version of BR support for Message logging has been added to BR in the form
of a new built in function:

debug_str(LogLevel:integer; Message:string)

This function can be used where ever you want in any program to provide
logging type of functionality for debugging purposes. It works on a
couple of different levels. If you have no debugger running against a
program, ie your customer is running the application, then depending on
your chosen logging command in the wbconfig.sys file only certain
messages that corresponds to the loglevel number will be logged. If
logging is turned off completely then no messages are logged at all. It
simply becomes a silent function call that does nothing.

If you have a debugger running against the program, the log messages
get sent directly to the debugger and show up on the Debugger tab of the
Messages tool window. BR will also send messages to the window, mostly
they will be BR debugging messages.

MyEditBR provides the means necessary to ignore all logging messages to
to log messages up to certain log levels. The higher the log level the
less important the message is deemed to be, as far as BR is concerned. BR
has specified that they use log level messages from 0 to 10.
MyEditBR allows you to filter messages from 0 to 10. While any number can
be used for a log level, if you want your messages to show up in MyEditBRs
Messages window, it must be log level 10 or less.

If you have BRSupport installed and running you can now see log messages
from it as well.

The configuration setting for both of these can be found on the Options
dialog under Debugger and BR Support respectively.

* Show Same Items

Now for those who don't know me, I'm all for taking a feature from
another project/product and trying to re-implement it in MyEditBR. Show
Same Items is one of those features and it currently only works for BR
source files. There is a new tool bar button that when pressed turns the
feature on. When on, as you cursor through your source code it will
highlight all instances of a token (ie variable) visible on the screen.

So for example if you have this feature enabled and you place your
cursor on the variable VAR1$ then every VAR1$ on the screen will become
highlighted. The colors are set in the Editor Options dialog for the
Business Rules color definitions. (*NOTE*: You may want to configure the
colors before trying to use this feature)

* Expanded Messages tool window

The newly expanded Messages tool window has tabs for the following
message types:

+ Plugins
+ System (MyEditBR)
+ BR Support
+ Debugger

* New Automatic Updating (v3 of the AutoUpdater)

The new automatic updating now allows for Multiple files to be updated
as well as providing information about each file. The update
information messages will now appear on the system tab of the messages
window. This is better than the older update system (v2) in that the
old system only could update the actual .EXE and nothing else.

* New Hints, Warnings and Errors
- 2000 character line limit. (BR v4.2+)
- FNKEY keyword has been deprecated (BR v4.2+)

Bugs Fixed:

- REM comment causing an orphaned line error message
- Additional $ appearing from the code completion wizard when used to
complete a $ terminated token.
- BR Support has been updated to v4.2+

I've fixed a number of other ones as well, but like I said I don't have
all of my information available to me this morning so I can't provide
more than that.

Known Bugs:

There are still a couple of known issues, but I wanted to get this
version released now instead of waiting for them to be fixed. Here is
the list of current known bugs:

- BR Load source from file
and
- Compile BR source to file:

This has been broken somehow, I think it has to do with the new version
of BRSupport that I use (BRv4.2). I'm working with Dan to try and
figure out whether it is something I've done (most likely) or something
to do with the new version of BR. This is currenly borked, so please
don't play with it.

If you have any problems please let me know, I would prefer to have bugs
registered on the support forums (http://support.mills-enterprise.ca)
but will accept br-forum messages as well as personal emails.

Thanks,

Ryan Mills
Mills Enterprise Ltd.





_______________________________________________
BR_forum mailing list
BR_forum@ads.net
http://ads.net/mailman/listinfo/br_forum_ads.net


_______________________________________________
BR_forum mailing list
BR_forum@ads.net
http://ads.net/mailman/listinfo/br_forum_ads.net
John Bowman

rmills

[BR_forum] MyEditBR v3.1.0.3300 Released

Postby rmills » Tue Jun 02, 2009 11:05 am

Sure there is.

Open the Editor Options dialog. Go to the Miscellaneous page
and find the Alternative Program Actions group box. Inside you'll
find the Close Application With No Prompts checkbox.

Ryan

Isn't there a setting to tell it not to prompt for save on exit? I
thought
there was but I'm having difficulty finding it now.

-----Original Message-----
From: br_forum-bounces@ads.net [mailto:br_forum-bounces@ads.net] On Behalf
Of
rmills@mills-enterprise.ca
Sent: Monday, June 01, 2009 11:33 AM
To: Business Rules Forum
Subject: [BR_forum] MyEditBR v3.1.0.3300 Released

Good Morning,

I've released a new version of MyEditBR.

For those who have the support licenses and a recent version of
MyEditBR.exe installed you should be able to use the help menu item "Check
for Updates..." to get the latest release.

Or is you prefer to install a clean copy you can download a new installer
from my website: http://www.mills-enterprise.ca

This version is the first to have direct support for BRv4.2 and some of
the new features found in that release version.

Normally I have a list of new features and bug fixes that I provide in
these announcements, but I forgot my list at home this morning. So I'll
try and provide a list from memory. So forgive me if I miss anything.

New features:

* MyEditBR Debugger Breakpoints

While this feature is not new in and of itself, the debugger
breakpoints have been greatly expanded to provide greater flexability.

New support has been added in MyEditBR to provide better support for
existing BR functionality.

MyEditBR now supports the following break point types:
+ Variable
+ Function
+ Program
+ Line Numbers

Valid support license holders also have new breakpoint functionality as
well. In addition to conditional breakpoint testing there is now a
feature call Pass Counts. The way that Pass Counts work is that if you
set any kind of breakpoint (Var, FN, Program, Line #) and then set a Pass
Count of 5 then the breakpoint doesn't actually happen in MyEditBR until
MyEditBR has detected that the break point position has been passed 5
times.

The Pass Count condition is faster that the Conditional check in that
MyEditBR doesn't have to have a conversation with BR to see if it's time
to return control to the debugger and user. Pass Counts and the
Conditional checks can also be combined to work in tandem. The way that
this works is that you specify a valid break point, a break point
Conditional test and a Pass Count number then run the application. The
MyEditBR debugger then waits until the Pass Count has been triggered
before starting to test the Conditional check. Once both have been
satisfied then the Breakpoint occurs and control is returned to the
Debugger and programmer.

* Debugger Log Messages (BRv4.2+)

MyEditBR has, for a long time had, a messages tool window that for most
people probably did nothing. That has now changed. With the latest
version of BR support for Message logging has been added to BR in the form
of a new built in function:

debug_str(LogLevel:integer; Message:string)

This function can be used where ever you want in any program to provide
logging type of functionality for debugging purposes. It works on a
couple of different levels. If you have no debugger running against a
program, ie your customer is running the application, then depending on
your chosen logging command in the wbconfig.sys file only certain
messages that corresponds to the loglevel number will be logged. If
logging is turned off completely then no messages are logged at all. It
simply becomes a silent function call that does nothing.

If you have a debugger running against the program, the log messages
get sent directly to the debugger and show up on the Debugger tab of the
Messages tool window. BR will also send messages to the window, mostly
they will be BR debugging messages.

MyEditBR provides the means necessary to ignore all logging messages to
to log messages up to certain log levels. The higher the log level the
less important the message is deemed to be, as far as BR is concerned. BR
has specified that they use log level messages from 0 to 10.
MyEditBR allows you to filter messages from 0 to 10. While any number can
be used for a log level, if you want your messages to show up in MyEditBRs
Messages window, it must be log level 10 or less.

If you have BRSupport installed and running you can now see log messages
from it as well.

The configuration setting for both of these can be found on the Options
dialog under Debugger and BR Support respectively.

* Show Same Items

Now for those who don't know me, I'm all for taking a feature from
another project/product and trying to re-implement it in MyEditBR. Show
Same Items is one of those features and it currently only works for BR
source files. There is a new tool bar button that when pressed turns the
feature on. When on, as you cursor through your source code it will
highlight all instances of a token (ie variable) visible on the screen.

So for example if you have this feature enabled and you place your
cursor on the variable VAR1$ then every VAR1$ on the screen will become
highlighted. The colors are set in the Editor Options dialog for the
Business Rules color definitions. (*NOTE*: You may want to configure the
colors before trying to use this feature)

* Expanded Messages tool window

The newly expanded Messages tool window has tabs for the following
message types:

+ Plugins
+ System (MyEditBR)
+ BR Support
+ Debugger

* New Automatic Updating (v3 of the AutoUpdater)

The new automatic updating now allows for Multiple files to be updated
as well as providing information about each file. The update
information messages will now appear on the system tab of the messages
window. This is better than the older update system (v2) in that the
old system only could update the actual .EXE and nothing else.

* New Hints, Warnings and Errors
- 2000 character line limit. (BR v4.2+)
- FNKEY keyword has been deprecated (BR v4.2+)

Bugs Fixed:

- REM comment causing an orphaned line error message
- Additional $ appearing from the code completion wizard when used to
complete a $ terminated token.
- BR Support has been updated to v4.2+

I've fixed a number of other ones as well, but like I said I don't have
all of my information available to me this morning so I can't provide
more than that.

Known Bugs:

There are still a couple of known issues, but I wanted to get this
version released now instead of waiting for them to be fixed. Here is
the list of current known bugs:

- BR Load source from file
and
- Compile BR source to file:

This has been broken somehow, I think it has to do with the new version
of BRSupport that I use (BRv4.2). I'm working with Dan to try and
figure out whether it is something I've done (most likely) or something
to do with the new version of BR. This is currenly borked, so please
don't play with it.

If you have any problems please let me know, I would prefer to have bugs
registered on the support forums (http://support.mills-enterprise.ca)
but will accept br-forum messages as well as personal emails.

Thanks,

Ryan Mills
Mills Enterprise Ltd.





_______________________________________________
BR_forum mailing list
BR_forum@ads.net
http://ads.net/mailman/listinfo/br_forum_ads.net


_______________________________________________
BR_forum mailing list
BR_forum@ads.net
http://ads.net/mailman/listinfo/br_forum_ads.net




_______________________________________________
BR_forum mailing list
BR_forum@ads.net
http://ads.net/mailman/listinfo/br_forum_ads.net

John
Posts: 507
Joined: Sun Apr 26, 2009 8:27 am
Location: West Orange, NJ
Contact:

[BR_forum] MyEditBR v3.1.0.3300 Released

Postby John » Tue Jun 02, 2009 11:11 am

Thank you, I added a check there. But it still prompts to save file changes on
exit. Am I misunderstanding something?

-----Original Message-----
From: br_forum-bounces@ads.net [mailto:br_forum-bounces@ads.net] On Behalf Of
rmills@mills-enterprise.ca
Sent: Tuesday, June 02, 2009 1:06 PM
To: Business Rules Forum
Subject: Re: [BR_forum] MyEditBR v3.1.0.3300 Released

Sure there is.

Open the Editor Options dialog. Go to the Miscellaneous page
and find the Alternative Program Actions group box. Inside you'll
find the Close Application With No Prompts checkbox.

Ryan

Isn't there a setting to tell it not to prompt for save on exit? I
thought
there was but I'm having difficulty finding it now.

-----Original Message-----
From: br_forum-bounces@ads.net [mailto:br_forum-bounces@ads.net] On Behalf
Of
rmills@mills-enterprise.ca
Sent: Monday, June 01, 2009 11:33 AM
To: Business Rules Forum
Subject: [BR_forum] MyEditBR v3.1.0.3300 Released

Good Morning,

I've released a new version of MyEditBR.

For those who have the support licenses and a recent version of
MyEditBR.exe installed you should be able to use the help menu item "Check
for Updates..." to get the latest release.

Or is you prefer to install a clean copy you can download a new installer
from my website: http://www.mills-enterprise.ca

This version is the first to have direct support for BRv4.2 and some of
the new features found in that release version.

Normally I have a list of new features and bug fixes that I provide in
these announcements, but I forgot my list at home this morning. So I'll
try and provide a list from memory. So forgive me if I miss anything.

New features:

* MyEditBR Debugger Breakpoints

While this feature is not new in and of itself, the debugger
breakpoints have been greatly expanded to provide greater flexability.

New support has been added in MyEditBR to provide better support for
existing BR functionality.

MyEditBR now supports the following break point types:
+ Variable
+ Function
+ Program
+ Line Numbers

Valid support license holders also have new breakpoint functionality as
well. In addition to conditional breakpoint testing there is now a
feature call Pass Counts. The way that Pass Counts work is that if you
set any kind of breakpoint (Var, FN, Program, Line #) and then set a Pass
Count of 5 then the breakpoint doesn't actually happen in MyEditBR until
MyEditBR has detected that the break point position has been passed 5
times.

The Pass Count condition is faster that the Conditional check in that
MyEditBR doesn't have to have a conversation with BR to see if it's time
to return control to the debugger and user. Pass Counts and the
Conditional checks can also be combined to work in tandem. The way that
this works is that you specify a valid break point, a break point
Conditional test and a Pass Count number then run the application. The
MyEditBR debugger then waits until the Pass Count has been triggered
before starting to test the Conditional check. Once both have been
satisfied then the Breakpoint occurs and control is returned to the
Debugger and programmer.

* Debugger Log Messages (BRv4.2+)

MyEditBR has, for a long time had, a messages tool window that for most
people probably did nothing. That has now changed. With the latest
version of BR support for Message logging has been added to BR in the form
of a new built in function:

debug_str(LogLevel:integer; Message:string)

This function can be used where ever you want in any program to provide
logging type of functionality for debugging purposes. It works on a
couple of different levels. If you have no debugger running against a
program, ie your customer is running the application, then depending on
your chosen logging command in the wbconfig.sys file only certain
messages that corresponds to the loglevel number will be logged. If
logging is turned off completely then no messages are logged at all. It
simply becomes a silent function call that does nothing.

If you have a debugger running against the program, the log messages
get sent directly to the debugger and show up on the Debugger tab of the
Messages tool window. BR will also send messages to the window, mostly
they will be BR debugging messages.

MyEditBR provides the means necessary to ignore all logging messages to
to log messages up to certain log levels. The higher the log level the
less important the message is deemed to be, as far as BR is concerned. BR
has specified that they use log level messages from 0 to 10.
MyEditBR allows you to filter messages from 0 to 10. While any number can
be used for a log level, if you want your messages to show up in MyEditBRs
Messages window, it must be log level 10 or less.

If you have BRSupport installed and running you can now see log messages
from it as well.

The configuration setting for both of these can be found on the Options
dialog under Debugger and BR Support respectively.

* Show Same Items

Now for those who don't know me, I'm all for taking a feature from
another project/product and trying to re-implement it in MyEditBR. Show
Same Items is one of those features and it currently only works for BR
source files. There is a new tool bar button that when pressed turns the
feature on. When on, as you cursor through your source code it will
highlight all instances of a token (ie variable) visible on the screen.

So for example if you have this feature enabled and you place your
cursor on the variable VAR1$ then every VAR1$ on the screen will become
highlighted. The colors are set in the Editor Options dialog for the
Business Rules color definitions. (*NOTE*: You may want to configure the
colors before trying to use this feature)

* Expanded Messages tool window

The newly expanded Messages tool window has tabs for the following
message types:

+ Plugins
+ System (MyEditBR)
+ BR Support
+ Debugger

* New Automatic Updating (v3 of the AutoUpdater)

The new automatic updating now allows for Multiple files to be updated
as well as providing information about each file. The update
information messages will now appear on the system tab of the messages
window. This is better than the older update system (v2) in that the
old system only could update the actual .EXE and nothing else.

* New Hints, Warnings and Errors
- 2000 character line limit. (BR v4.2+)
- FNKEY keyword has been deprecated (BR v4.2+)

Bugs Fixed:

- REM comment causing an orphaned line error message
- Additional $ appearing from the code completion wizard when used to
complete a $ terminated token.
- BR Support has been updated to v4.2+

I've fixed a number of other ones as well, but like I said I don't have
all of my information available to me this morning so I can't provide
more than that.

Known Bugs:

There are still a couple of known issues, but I wanted to get this
version released now instead of waiting for them to be fixed. Here is
the list of current known bugs:

- BR Load source from file
and
- Compile BR source to file:

This has been broken somehow, I think it has to do with the new version
of BRSupport that I use (BRv4.2). I'm working with Dan to try and
figure out whether it is something I've done (most likely) or something
to do with the new version of BR. This is currenly borked, so please
don't play with it.

If you have any problems please let me know, I would prefer to have bugs
registered on the support forums (http://support.mills-enterprise.ca)
but will accept br-forum messages as well as personal emails.

Thanks,

Ryan Mills
Mills Enterprise Ltd.





_______________________________________________
BR_forum mailing list
BR_forum@ads.net
http://ads.net/mailman/listinfo/br_forum_ads.net


_______________________________________________
BR_forum mailing list
BR_forum@ads.net
http://ads.net/mailman/listinfo/br_forum_ads.net




_______________________________________________
BR_forum mailing list
BR_forum@ads.net
http://ads.net/mailman/listinfo/br_forum_ads.net


_______________________________________________
BR_forum mailing list
BR_forum@ads.net
http://ads.net/mailman/listinfo/br_forum_ads.net
John Bowman

rmills

[BR_forum] MyEditBR v3.1.0.3300 Released

Postby rmills » Tue Jun 02, 2009 11:14 am

I though this was working.

Do you remember the command line option I told you about to force this?

Try that.

I'll have to take a look at this tonight.

Ryan.

Thank you, I added a check there. But it still prompts to save file
changes on
exit. Am I misunderstanding something?

-----Original Message-----
From: br_forum-bounces@ads.net [mailto:br_forum-bounces@ads.net] On Behalf
Of
rmills@mills-enterprise.ca
Sent: Tuesday, June 02, 2009 1:06 PM
To: Business Rules Forum
Subject: Re: [BR_forum] MyEditBR v3.1.0.3300 Released

Sure there is.

Open the Editor Options dialog. Go to the Miscellaneous page
and find the Alternative Program Actions group box. Inside you'll
find the Close Application With No Prompts checkbox.

Ryan

Isn't there a setting to tell it not to prompt for save on exit? I
thought
there was but I'm having difficulty finding it now.

-----Original Message-----
From: br_forum-bounces@ads.net [mailto:br_forum-bounces@ads.net] On
Behalf
Of
rmills@mills-enterprise.ca
Sent: Monday, June 01, 2009 11:33 AM
To: Business Rules Forum
Subject: [BR_forum] MyEditBR v3.1.0.3300 Released

Good Morning,

I've released a new version of MyEditBR.

For those who have the support licenses and a recent version of
MyEditBR.exe installed you should be able to use the help menu item
"Check
for Updates..." to get the latest release.

Or is you prefer to install a clean copy you can download a new
installer
from my website: http://www.mills-enterprise.ca

This version is the first to have direct support for BRv4.2 and some of
the new features found in that release version.

Normally I have a list of new features and bug fixes that I provide in
these announcements, but I forgot my list at home this morning. So I'll
try and provide a list from memory. So forgive me if I miss anything.

New features:

* MyEditBR Debugger Breakpoints

While this feature is not new in and of itself, the debugger
breakpoints have been greatly expanded to provide greater
flexability.

New support has been added in MyEditBR to provide better support for
existing BR functionality.

MyEditBR now supports the following break point types:
+ Variable
+ Function
+ Program
+ Line Numbers

Valid support license holders also have new breakpoint functionality
as
well. In addition to conditional breakpoint testing there is now a
feature call Pass Counts. The way that Pass Counts work is that if you
set any kind of breakpoint (Var, FN, Program, Line #) and then set a
Pass
Count of 5 then the breakpoint doesn't actually happen in MyEditBR until
MyEditBR has detected that the break point position has been passed 5
times.

The Pass Count condition is faster that the Conditional check in that
MyEditBR doesn't have to have a conversation with BR to see if it's time
to return control to the debugger and user. Pass Counts and the
Conditional checks can also be combined to work in tandem. The way that
this works is that you specify a valid break point, a break point
Conditional test and a Pass Count number then run the application. The
MyEditBR debugger then waits until the Pass Count has been triggered
before starting to test the Conditional check. Once both have been
satisfied then the Breakpoint occurs and control is returned to the
Debugger and programmer.

* Debugger Log Messages (BRv4.2+)

MyEditBR has, for a long time had, a messages tool window that for
most
people probably did nothing. That has now changed. With the latest
version of BR support for Message logging has been added to BR in the
form
of a new built in function:

debug_str(LogLevel:integer; Message:string)

This function can be used where ever you want in any program to
provide
logging type of functionality for debugging purposes. It works on a
couple of different levels. If you have no debugger running against a
program, ie your customer is running the application, then depending on
your chosen logging command in the wbconfig.sys file only certain
messages that corresponds to the loglevel number will be logged. If
logging is turned off completely then no messages are logged at all. It
simply becomes a silent function call that does nothing.

If you have a debugger running against the program, the log messages
get sent directly to the debugger and show up on the Debugger tab of the
Messages tool window. BR will also send messages to the window, mostly
they will be BR debugging messages.

MyEditBR provides the means necessary to ignore all logging messages
to
to log messages up to certain log levels. The higher the log level the
less important the message is deemed to be, as far as BR is concerned.
BR
has specified that they use log level messages from 0 to 10.
MyEditBR allows you to filter messages from 0 to 10. While any number
can
be used for a log level, if you want your messages to show up in
MyEditBRs
Messages window, it must be log level 10 or less.

If you have BRSupport installed and running you can now see log messages
from it as well.

The configuration setting for both of these can be found on the Options
dialog under Debugger and BR Support respectively.

* Show Same Items

Now for those who don't know me, I'm all for taking a feature from
another project/product and trying to re-implement it in MyEditBR. Show
Same Items is one of those features and it currently only works for BR
source files. There is a new tool bar button that when pressed turns
the
feature on. When on, as you cursor through your source code it will
highlight all instances of a token (ie variable) visible on the screen.

So for example if you have this feature enabled and you place your
cursor on the variable VAR1$ then every VAR1$ on the screen will become
highlighted. The colors are set in the Editor Options dialog for the
Business Rules color definitions. (*NOTE*: You may want to configure
the
colors before trying to use this feature)

* Expanded Messages tool window

The newly expanded Messages tool window has tabs for the following
message types:

+ Plugins
+ System (MyEditBR)
+ BR Support
+ Debugger

* New Automatic Updating (v3 of the AutoUpdater)

The new automatic updating now allows for Multiple files to be
updated
as well as providing information about each file. The update
information messages will now appear on the system tab of the messages
window. This is better than the older update system (v2) in that the
old system only could update the actual .EXE and nothing else.

* New Hints, Warnings and Errors
- 2000 character line limit. (BR v4.2+)
- FNKEY keyword has been deprecated (BR v4.2+)

Bugs Fixed:

- REM comment causing an orphaned line error message
- Additional $ appearing from the code completion wizard when used to
complete a $ terminated token.
- BR Support has been updated to v4.2+

I've fixed a number of other ones as well, but like I said I don't
have
all of my information available to me this morning so I can't provide
more than that.

Known Bugs:

There are still a couple of known issues, but I wanted to get this
version released now instead of waiting for them to be fixed. Here is
the list of current known bugs:

- BR Load source from file
and
- Compile BR source to file:

This has been broken somehow, I think it has to do with the new
version
of BRSupport that I use (BRv4.2). I'm working with Dan to try and
figure out whether it is something I've done (most likely) or something
to do with the new version of BR. This is currenly borked, so please
don't play with it.

If you have any problems please let me know, I would prefer to have bugs
registered on the support forums (http://support.mills-enterprise.ca)
but will accept br-forum messages as well as personal emails.

Thanks,

Ryan Mills
Mills Enterprise Ltd.





_______________________________________________
BR_forum mailing list
BR_forum@ads.net
http://ads.net/mailman/listinfo/br_forum_ads.net


_______________________________________________
BR_forum mailing list
BR_forum@ads.net
http://ads.net/mailman/listinfo/br_forum_ads.net




_______________________________________________
BR_forum mailing list
BR_forum@ads.net
http://ads.net/mailman/listinfo/br_forum_ads.net


_______________________________________________
BR_forum mailing list
BR_forum@ads.net
http://ads.net/mailman/listinfo/br_forum_ads.net




_______________________________________________
BR_forum mailing list
BR_forum@ads.net
http://ads.net/mailman/listinfo/br_forum_ads.net

John
Posts: 507
Joined: Sun Apr 26, 2009 8:27 am
Location: West Orange, NJ
Contact:

[BR_forum] MyEditBR v3.1.0.3300 Released

Postby John » Tue Jun 02, 2009 11:16 am

The command line option is /AutoFCReload. I am using it. I believe it causes
the document to automatically reload whenever the source file changes.

-john

-----Original Message-----
From: br_forum-bounces@ads.net [mailto:br_forum-bounces@ads.net] On Behalf Of
rmills@mills-enterprise.ca
Sent: Tuesday, June 02, 2009 1:15 PM
To: Business Rules Forum
Subject: Re: [BR_forum] MyEditBR v3.1.0.3300 Released

I though this was working.

Do you remember the command line option I told you about to force this?

Try that.

I'll have to take a look at this tonight.

Ryan.

Thank you, I added a check there. But it still prompts to save file
changes on
exit. Am I misunderstanding something?

-----Original Message-----
From: br_forum-bounces@ads.net [mailto:br_forum-bounces@ads.net] On Behalf
Of
rmills@mills-enterprise.ca
Sent: Tuesday, June 02, 2009 1:06 PM
To: Business Rules Forum
Subject: Re: [BR_forum] MyEditBR v3.1.0.3300 Released

Sure there is.

Open the Editor Options dialog. Go to the Miscellaneous page
and find the Alternative Program Actions group box. Inside you'll
find the Close Application With No Prompts checkbox.

Ryan

Isn't there a setting to tell it not to prompt for save on exit? I
thought
there was but I'm having difficulty finding it now.

-----Original Message-----
From: br_forum-bounces@ads.net [mailto:br_forum-bounces@ads.net] On
Behalf
Of
rmills@mills-enterprise.ca
Sent: Monday, June 01, 2009 11:33 AM
To: Business Rules Forum
Subject: [BR_forum] MyEditBR v3.1.0.3300 Released

Good Morning,

I've released a new version of MyEditBR.

For those who have the support licenses and a recent version of
MyEditBR.exe installed you should be able to use the help menu item
"Check
for Updates..." to get the latest release.

Or is you prefer to install a clean copy you can download a new
installer
from my website: http://www.mills-enterprise.ca

This version is the first to have direct support for BRv4.2 and some of
the new features found in that release version.

Normally I have a list of new features and bug fixes that I provide in
these announcements, but I forgot my list at home this morning. So I'll
try and provide a list from memory. So forgive me if I miss anything.

New features:

* MyEditBR Debugger Breakpoints

While this feature is not new in and of itself, the debugger
breakpoints have been greatly expanded to provide greater
flexability.

New support has been added in MyEditBR to provide better support for
existing BR functionality.

MyEditBR now supports the following break point types:
+ Variable
+ Function
+ Program
+ Line Numbers

Valid support license holders also have new breakpoint functionality
as
well. In addition to conditional breakpoint testing there is now a
feature call Pass Counts. The way that Pass Counts work is that if you
set any kind of breakpoint (Var, FN, Program, Line #) and then set a
Pass
Count of 5 then the breakpoint doesn't actually happen in MyEditBR until
MyEditBR has detected that the break point position has been passed 5
times.

The Pass Count condition is faster that the Conditional check in that
MyEditBR doesn't have to have a conversation with BR to see if it's time
to return control to the debugger and user. Pass Counts and the
Conditional checks can also be combined to work in tandem. The way that
this works is that you specify a valid break point, a break point
Conditional test and a Pass Count number then run the application. The
MyEditBR debugger then waits until the Pass Count has been triggered
before starting to test the Conditional check. Once both have been
satisfied then the Breakpoint occurs and control is returned to the
Debugger and programmer.

* Debugger Log Messages (BRv4.2+)

MyEditBR has, for a long time had, a messages tool window that for
most
people probably did nothing. That has now changed. With the latest
version of BR support for Message logging has been added to BR in the
form
of a new built in function:

debug_str(LogLevel:integer; Message:string)

This function can be used where ever you want in any program to
provide
logging type of functionality for debugging purposes. It works on a
couple of different levels. If you have no debugger running against a
program, ie your customer is running the application, then depending on
your chosen logging command in the wbconfig.sys file only certain
messages that corresponds to the loglevel number will be logged. If
logging is turned off completely then no messages are logged at all. It
simply becomes a silent function call that does nothing.

If you have a debugger running against the program, the log messages
get sent directly to the debugger and show up on the Debugger tab of the
Messages tool window. BR will also send messages to the window, mostly
they will be BR debugging messages.

MyEditBR provides the means necessary to ignore all logging messages
to
to log messages up to certain log levels. The higher the log level the
less important the message is deemed to be, as far as BR is concerned.
BR
has specified that they use log level messages from 0 to 10.
MyEditBR allows you to filter messages from 0 to 10. While any number
can
be used for a log level, if you want your messages to show up in
MyEditBRs
Messages window, it must be log level 10 or less.

If you have BRSupport installed and running you can now see log messages
from it as well.

The configuration setting for both of these can be found on the Options
dialog under Debugger and BR Support respectively.

* Show Same Items

Now for those who don't know me, I'm all for taking a feature from
another project/product and trying to re-implement it in MyEditBR. Show
Same Items is one of those features and it currently only works for BR
source files. There is a new tool bar button that when pressed turns
the
feature on. When on, as you cursor through your source code it will
highlight all instances of a token (ie variable) visible on the screen.

So for example if you have this feature enabled and you place your
cursor on the variable VAR1$ then every VAR1$ on the screen will become
highlighted. The colors are set in the Editor Options dialog for the
Business Rules color definitions. (*NOTE*: You may want to configure
the
colors before trying to use this feature)

* Expanded Messages tool window

The newly expanded Messages tool window has tabs for the following
message types:

+ Plugins
+ System (MyEditBR)
+ BR Support
+ Debugger

* New Automatic Updating (v3 of the AutoUpdater)

The new automatic updating now allows for Multiple files to be
updated
as well as providing information about each file. The update
information messages will now appear on the system tab of the messages
window. This is better than the older update system (v2) in that the
old system only could update the actual .EXE and nothing else.

* New Hints, Warnings and Errors
- 2000 character line limit. (BR v4.2+)
- FNKEY keyword has been deprecated (BR v4.2+)

Bugs Fixed:

- REM comment causing an orphaned line error message
- Additional $ appearing from the code completion wizard when used to
complete a $ terminated token.
- BR Support has been updated to v4.2+

I've fixed a number of other ones as well, but like I said I don't
have
all of my information available to me this morning so I can't provide
more than that.

Known Bugs:

There are still a couple of known issues, but I wanted to get this
version released now instead of waiting for them to be fixed. Here is
the list of current known bugs:

- BR Load source from file
and
- Compile BR source to file:

This has been broken somehow, I think it has to do with the new
version
of BRSupport that I use (BRv4.2). I'm working with Dan to try and
figure out whether it is something I've done (most likely) or something
to do with the new version of BR. This is currenly borked, so please
don't play with it.

If you have any problems please let me know, I would prefer to have bugs
registered on the support forums (http://support.mills-enterprise.ca)
but will accept br-forum messages as well as personal emails.

Thanks,

Ryan Mills
Mills Enterprise Ltd.





_______________________________________________
BR_forum mailing list
BR_forum@ads.net
http://ads.net/mailman/listinfo/br_forum_ads.net


_______________________________________________
BR_forum mailing list
BR_forum@ads.net
http://ads.net/mailman/listinfo/br_forum_ads.net




_______________________________________________
BR_forum mailing list
BR_forum@ads.net
http://ads.net/mailman/listinfo/br_forum_ads.net


_______________________________________________
BR_forum mailing list
BR_forum@ads.net
http://ads.net/mailman/listinfo/br_forum_ads.net




_______________________________________________
BR_forum mailing list
BR_forum@ads.net
http://ads.net/mailman/listinfo/br_forum_ads.net


_______________________________________________
BR_forum mailing list
BR_forum@ads.net
http://ads.net/mailman/listinfo/br_forum_ads.net
John Bowman

rmills

[BR_forum] MyEditBR v3.1.0.3300 Released

Postby rmills » Tue Jun 02, 2009 11:24 am

OK.

I'll have to take a look at it then. I haven't touched that feature, so
I'm not sure why it's not working.

Ryan.

The command line option is /AutoFCReload. I am using it. I believe it
causes
the document to automatically reload whenever the source file changes.

-john

-----Original Message-----
From: br_forum-bounces@ads.net [mailto:br_forum-bounces@ads.net] On Behalf
Of
rmills@mills-enterprise.ca
Sent: Tuesday, June 02, 2009 1:15 PM
To: Business Rules Forum
Subject: Re: [BR_forum] MyEditBR v3.1.0.3300 Released

I though this was working.

Do you remember the command line option I told you about to force this?

Try that.

I'll have to take a look at this tonight.

Ryan.

Thank you, I added a check there. But it still prompts to save file
changes on
exit. Am I misunderstanding something?

-----Original Message-----
From: br_forum-bounces@ads.net [mailto:br_forum-bounces@ads.net] On
Behalf
Of
rmills@mills-enterprise.ca
Sent: Tuesday, June 02, 2009 1:06 PM
To: Business Rules Forum
Subject: Re: [BR_forum] MyEditBR v3.1.0.3300 Released

Sure there is.

Open the Editor Options dialog. Go to the Miscellaneous page
and find the Alternative Program Actions group box. Inside you'll
find the Close Application With No Prompts checkbox.

Ryan

Isn't there a setting to tell it not to prompt for save on exit? I
thought
there was but I'm having difficulty finding it now.

-----Original Message-----
From: br_forum-bounces@ads.net [mailto:br_forum-bounces@ads.net] On
Behalf
Of
rmills@mills-enterprise.ca
Sent: Monday, June 01, 2009 11:33 AM
To: Business Rules Forum
Subject: [BR_forum] MyEditBR v3.1.0.3300 Released

Good Morning,

I've released a new version of MyEditBR.

For those who have the support licenses and a recent version of
MyEditBR.exe installed you should be able to use the help menu item
"Check
for Updates..." to get the latest release.

Or is you prefer to install a clean copy you can download a new
installer
from my website: http://www.mills-enterprise.ca

This version is the first to have direct support for BRv4.2 and some of
the new features found in that release version.

Normally I have a list of new features and bug fixes that I provide in
these announcements, but I forgot my list at home this morning. So
I'll
try and provide a list from memory. So forgive me if I miss anything.

New features:

* MyEditBR Debugger Breakpoints

While this feature is not new in and of itself, the debugger
breakpoints have been greatly expanded to provide greater
flexability.

New support has been added in MyEditBR to provide better support for
existing BR functionality.

MyEditBR now supports the following break point types:
+ Variable
+ Function
+ Program
+ Line Numbers

Valid support license holders also have new breakpoint functionality
as
well. In addition to conditional breakpoint testing there is now a
feature call Pass Counts. The way that Pass Counts work is that if you
set any kind of breakpoint (Var, FN, Program, Line #) and then set a
Pass
Count of 5 then the breakpoint doesn't actually happen in MyEditBR
until
MyEditBR has detected that the break point position has been passed 5
times.

The Pass Count condition is faster that the Conditional check in
that
MyEditBR doesn't have to have a conversation with BR to see if it's
time
to return control to the debugger and user. Pass Counts and the
Conditional checks can also be combined to work in tandem. The way
that
this works is that you specify a valid break point, a break point
Conditional test and a Pass Count number then run the application. The
MyEditBR debugger then waits until the Pass Count has been triggered
before starting to test the Conditional check. Once both have been
satisfied then the Breakpoint occurs and control is returned to the
Debugger and programmer.

* Debugger Log Messages (BRv4.2+)

MyEditBR has, for a long time had, a messages tool window that for
most
people probably did nothing. That has now changed. With the latest
version of BR support for Message logging has been added to BR in the
form
of a new built in function:

debug_str(LogLevel:integer; Message:string)

This function can be used where ever you want in any program to
provide
logging type of functionality for debugging purposes. It works on a
couple of different levels. If you have no debugger running against a
program, ie your customer is running the application, then depending on
your chosen logging command in the wbconfig.sys file only certain
messages that corresponds to the loglevel number will be logged. If
logging is turned off completely then no messages are logged at all. It
simply becomes a silent function call that does nothing.

If you have a debugger running against the program, the log messages
get sent directly to the debugger and show up on the Debugger tab of
the
Messages tool window. BR will also send messages to the window, mostly
they will be BR debugging messages.

MyEditBR provides the means necessary to ignore all logging messages
to
to log messages up to certain log levels. The higher the log level the
less important the message is deemed to be, as far as BR is concerned.
BR
has specified that they use log level messages from 0 to 10.
MyEditBR allows you to filter messages from 0 to 10. While any number
can
be used for a log level, if you want your messages to show up in
MyEditBRs
Messages window, it must be log level 10 or less.

If you have BRSupport installed and running you can now see log
messages
from it as well.

The configuration setting for both of these can be found on the Options
dialog under Debugger and BR Support respectively.

* Show Same Items

Now for those who don't know me, I'm all for taking a feature from
another project/product and trying to re-implement it in MyEditBR.
Show
Same Items is one of those features and it currently only works for BR
source files. There is a new tool bar button that when pressed turns
the
feature on. When on, as you cursor through your source code it will
highlight all instances of a token (ie variable) visible on the screen.

So for example if you have this feature enabled and you place your
cursor on the variable VAR1$ then every VAR1$ on the screen will become
highlighted. The colors are set in the Editor Options dialog for the
Business Rules color definitions. (*NOTE*: You may want to configure
the
colors before trying to use this feature)

* Expanded Messages tool window

The newly expanded Messages tool window has tabs for the following
message types:

+ Plugins
+ System (MyEditBR)
+ BR Support
+ Debugger

* New Automatic Updating (v3 of the AutoUpdater)

The new automatic updating now allows for Multiple files to be
updated
as well as providing information about each file. The update
information messages will now appear on the system tab of the messages
window. This is better than the older update system (v2) in that the
old system only could update the actual .EXE and nothing else.

* New Hints, Warnings and Errors
- 2000 character line limit. (BR v4.2+)
- FNKEY keyword has been deprecated (BR v4.2+)

Bugs Fixed:

- REM comment causing an orphaned line error message
- Additional $ appearing from the code completion wizard when used to
complete a $ terminated token.
- BR Support has been updated to v4.2+

I've fixed a number of other ones as well, but like I said I don't
have
all of my information available to me this morning so I can't provide
more than that.

Known Bugs:

There are still a couple of known issues, but I wanted to get this
version released now instead of waiting for them to be fixed. Here is
the list of current known bugs:

- BR Load source from file
and
- Compile BR source to file:

This has been broken somehow, I think it has to do with the new
version
of BRSupport that I use (BRv4.2). I'm working with Dan to try and
figure out whether it is something I've done (most likely) or something
to do with the new version of BR. This is currenly borked, so please
don't play with it.

If you have any problems please let me know, I would prefer to have
bugs
registered on the support forums (http://support.mills-enterprise.ca)
but will accept br-forum messages as well as personal emails.

Thanks,

Ryan Mills
Mills Enterprise Ltd.





_______________________________________________
BR_forum mailing list
BR_forum@ads.net
http://ads.net/mailman/listinfo/br_forum_ads.net


_______________________________________________
BR_forum mailing list
BR_forum@ads.net
http://ads.net/mailman/listinfo/br_forum_ads.net




_______________________________________________
BR_forum mailing list
BR_forum@ads.net
http://ads.net/mailman/listinfo/br_forum_ads.net


_______________________________________________
BR_forum mailing list
BR_forum@ads.net
http://ads.net/mailman/listinfo/br_forum_ads.net




_______________________________________________
BR_forum mailing list
BR_forum@ads.net
http://ads.net/mailman/listinfo/br_forum_ads.net


_______________________________________________
BR_forum mailing list
BR_forum@ads.net
http://ads.net/mailman/listinfo/br_forum_ads.net




_______________________________________________
BR_forum mailing list
BR_forum@ads.net
http://ads.net/mailman/listinfo/br_forum_ads.net

Susan Smith
Posts: 654
Joined: Sun Aug 10, 2008 4:24 am
Location: Southern California

[BR_forum] MyEditBR v3.1.0.3300 Released

Postby Susan Smith » Tue Jun 02, 2009 11:28 am

Hi Ryan,

When I click on the "check for updates" link in MyEdit, a window pops up that says "You've reached the Mills Enterprise automated Web Support area". Am I supposed to do something at this point? All I can do is click to close that window. If I download an entire clean install instead, will I need to re-install my license and set up my custom colors?

I can't wait to try the "Show Same Items" feature. That sounds like a godsend to me!

-- Susan

rmills@mills-enterprise.ca (rmills@mills-enterprise.ca) wrote:
Good Morning,

I've released a new version of MyEditBR.

For those who have the support licenses and a recent version of
MyEditBR.exe installed you should be able to use the help menu item "Check
for Updates..." to get the latest release.

John
Posts: 507
Joined: Sun Apr 26, 2009 8:27 am
Location: West Orange, NJ
Contact:

[BR_forum] MyEditBR v3.1.0.3300 Released

Postby John » Tue Jun 02, 2009 11:35 am

Notepad++ has that feature too, Susan and it is indeed a godsend!

From: br_forum-bounces@ads.net [mailto:br_forum-bounces@ads.net] On Behalf Of Susan Smith
Sent: Tuesday, June 02, 2009 1:28 PM
To: Business Rules Forum
Subject: Re: [BR_forum] MyEditBR v3.1.0.3300 Released



Hi Ryan,

When I click on the "check for updates" link in MyEdit, a window pops up that says "You've reached the Mills Enterprise automated Web Support area". Am I supposed to do something at this point? All I can do is click to close that window. If I download an entire clean install instead, will I need to re-install my license and set up my custom colors?

I can't wait to try the "Show Same Items" feature. That sounds like a godsend to me!

-- Susan

rmills@mills-enterprise.ca (rmills@mills-enterprise.ca) wrote:
Good Morning, I've released a new version of MyEditBR. For those who have the support licenses and a recent version ofMyEditBR.exe installed you should be able to use the help menu item "Checkfor Updates..." to get the latest release.
John Bowman

rmills

[BR_forum] MyEditBR v3.1.0.3300 Released

Postby rmills » Tue Jun 02, 2009 11:57 am

Hi Susan,

You'll have to down load the full install from the website. You have a
really old version of the update system (v1) which only checked for the
existence of an update.

You should be able to either install over top of your existing setup, or
uninstall the old one and then install the new one and your settings and
license file should be fine in either case.

Ryan.

Hi Ryan,<br>
<br>
When I click on the "check for updates" link in MyEdit, a window pops
up that says "You've reached the Mills Enterprise automated Web Support
area". Am I supposed to do something at this point? All I can do is
click to close that window.&nbsp; If I download an entire clean install
instead, will I need to re-install my license and set up my custom
colors?<br>
<br>
I can't wait to try the "Show Same Items" feature. That sounds like a
godsend to me!<br>
<br>



_______________________________________________
BR_forum mailing list
BR_forum@ads.net
http://ads.net/mailman/listinfo/br_forum_ads.net

Susan Smith
Posts: 654
Joined: Sun Aug 10, 2008 4:24 am
Location: Southern California

[BR_forum] MyEditBR v3.1.0.3300 Released

Postby Susan Smith » Tue Jun 02, 2009 12:15 pm

Thank you Ryan. I just installed the new version. I can verify that installing the new version over your previous version (without uninstalling the old one first) it DOES retain your colors and installed tools, but you WILL need to reinstall your license. This was not a problem of course and I'm all set up now.

-- Susan


rmills@mills-enterprise.ca (rmills@mills-enterprise.ca) wrote:
Hi Susan,

You'll have to down load the full install from the website. You have a
really old version of the update system (v1) which only checked for the
existence of an update.

You should be able to either install over top of your existing setup, or
uninstall the old one and then install the new one and your settings and
license file should be fine in either case.

Ryan.

Hi Ryan,<br>
<br>
When I click on the "check for updates" link in MyEdit, a window pops
up that says "You've reached the Mills Enterprise automated Web Support
area". Am I supposed to do something at this point? All I can do is
click to close that window.&nbsp; If I download an entire clean install
instead, will I need to re-install my license and set up my custom
colors?<br>
<br>
I can't wait to try the "Show Same Items" feature. That sounds like a
godsend to me!<br>
<br>

rmills

[BR_forum] MyEditBR v3.1.0.3300 Released

Postby rmills » Tue Jun 02, 2009 12:19 pm

Thanks for the information Susan.

I'll make sure to fix that for the future.

Ryan.

Thank you Ryan. I just installed the new version. I can verify that
installing the new version over your previous version (without
uninstalling the old one first) it DOES retain your colors and
installed tools, but you WILL need to reinstall your license. This was
not a problem of course and I'm all set up now.<br>
<br>
-- Susan<br>



_______________________________________________
BR_forum mailing list
BR_forum@ads.net
http://ads.net/mailman/listinfo/br_forum_ads.net


Return to “3rd Party Software from the BR Community”

Who is online

Users browsing this forum: No registered users and 1 guest

cron