| View previous topic :: View next topic |
| Author |
Message |
Saulo I. Regis Guest
|
Posted: Fri May 21, 2004 1:23 pm Post subject: PlannedWeek++ |
|
|
Since last Friday each Friday adds a week delay to the "planned" release
date of the announced upcoming Open Letter!
This will be true until such Open Letter will be published!
Just to remember!
Today is the first iteration of PlannedWeek++
Saulo
|
|
| Back to top |
|
 |
Peter Agricola Guest
|
Posted: Fri May 21, 2004 5:28 pm Post subject: Re: PlannedWeek++ |
|
|
"Saulo I. Regis" wrote:
| Quote: | Since last Friday each Friday adds a week delay to the "planned" release
date of the announced upcoming Open Letter!
This will be true until such Open Letter will be published!
Just to remember!
Today is the first iteration of PlannedWeek++
|
++PlannedWeek is more effiecient. I'm not sure the difference is noticeable.
Peter
|
|
| Back to top |
|
 |
Saulo I. Regis Guest
|
Posted: Fri May 21, 2004 5:28 pm Post subject: Re: PlannedWeek++ |
|
|
Hi Peter,
| Quote: | ++PlannedWeek is more effiecient. I'm not sure the difference is
noticeable. |
Same thing! No sign of the Open Letter while iterating!
I was also thinking that may be "PlannedWeekDelay" could be a better name!
Saulo
|
|
| Back to top |
|
 |
Boian Mitov Guest
|
Posted: Fri May 21, 2004 7:14 pm Post subject: Re: PlannedWeek++ |
|
|
Check to see if there is a breakpoint placed there. It could be also
a debugger introduced delay. Try to compile the Borland.bpr without
debug information. You can also check if you have BCB DesperatePatch 4
installed. Try also to change the "Build with runtime OpenLetters"
Project Option. As a last resort, try to compile with a third party
OpenLetter. Also check if the OpenLetter.src and the OpenLetter.legal
header file are in sync. Some delays are due to inefficient *.legal
header file. Move some of the .legal functionality into the .src file.
This way the Borland will not have to compile the .legal file each time
it is included. Also try to put "#pragma legalstop" each place you use
the .legal file. This will result into generating a single one time
precompiled legal file for each of the files using it.
If nothing else works, roll back your clock, and pretend that the
OpanLetter-Day has not arrived. It usually fools the time sensitive
applications.
Please let us know, if it works for you. If it does not, we can try
burring our heads into the sand as alternative approach, however it
results in some other body parts sticking up high.
With best regards,
Boian Mitov
Saulo I. Regis wrote:
| Quote: |
Same thing! No sign of the Open Letter while iterating!
|
|
|
| Back to top |
|
 |
Dave Jewell Guest
|
Posted: Fri May 21, 2004 9:53 pm Post subject: Re: PlannedWeek++ |
|
|
"Saulo I. Regis" <saulo (AT) password (DOT) info> wrote
| Quote: | Today is the first iteration of PlannedWeek++
|
PlannedWeek++ is old hat. What you need is PlannedWeek#. It doesn't have
"pointers" to fictitious open letters, but you can be sure that everything
is properly "managed". Moreover, all "garbage" found in these newsgroups
will be rigorously collected.... :-)
Dave
|
|
| Back to top |
|
 |
DS Guest
|
Posted: Fri May 21, 2004 10:14 pm Post subject: Re: PlannedWeek++ |
|
|
Dave Jewell wrote:
| Quote: | PlannedWeek++ is old hat. What you need is PlannedWeek#. It doesn't have
"pointers" to fictitious open letters, but you can be sure that everything
is properly "managed". Moreover, all "garbage" found in these newsgroups
will be rigorously collected.... :-)
ROFLMAO!!! |
LP,
Dejan
|
|
| Back to top |
|
 |
Sebastian Ledesma Guest
|
Posted: Fri May 28, 2004 9:09 pm Post subject: Re: ++m_ulPlannedWeek [Was: Re: PlannedWeek++] |
|
|
I think we should re-code:
m_ulPlannedWeek = m_ulPlannedWeek <<1;
"Graham Reeds" <grahamr (AT) omnieng (DOT) co.uk> escribió en el mensaje
news:40b1ba62$1 (AT) newsgroups (DOT) borland.com...
|
|
| Back to top |
|
 |
|