eXpress++ Build 268 is released
Re: eXpress++ Build 268 is released
Damned dog.
Best regards,
Tom
"Did I offend you?"
"No."
"Okay, give me a second chance."
Tom
"Did I offend you?"
"No."
"Okay, give me a second chance."
Re: eXpress++ Build 268 is released
Yes, service was better in the past. Tom's remark let me think of the time before internet or pc-anywhere. This was the way our service worked.
- Customer had a problem and called us by phone. If the problem wasn't solved next step.
- Creation of a 5.25 disk with the first 20 records of each dbf file with a separate routine.
- Sending this disk by post to us. Normally it arrived the day after.
- Checking the databases and looking for a solution. In a lot of cases an update on disk, which was posted the same day.
- Next day the customer received the disk, and could do the update.
Customers were happy with this fast service.
Now when the phone rings, customers asks if we got their mail, and sometimes this is about 2 minutes after sending the mail.
- Customer had a problem and called us by phone. If the problem wasn't solved next step.
- Creation of a 5.25 disk with the first 20 records of each dbf file with a separate routine.
- Sending this disk by post to us. Normally it arrived the day after.
- Checking the databases and looking for a solution. In a lot of cases an update on disk, which was posted the same day.
- Next day the customer received the disk, and could do the update.
Customers were happy with this fast service.
Now when the phone rings, customers asks if we got their mail, and sometimes this is about 2 minutes after sending the mail.
Re: eXpress++ Build 268 is released
Chris -
we program software updates while the customer is on the phone, we deliver this immediatley in the background and it takes approximately 30 seconds until we ask the customer: If you click now, is everything fine again?
That is the standard we expect from others aswell (Roger comes close to that).
To be serious again, I remember those floppy-disk-sending-times very well. I remember things like "We need a copy of the disk" and received a photocopy some days later. Rolling out an update was a tremendous hassle. And so on ...
we program software updates while the customer is on the phone, we deliver this immediatley in the background and it takes approximately 30 seconds until we ask the customer: If you click now, is everything fine again?
That is the standard we expect from others aswell (Roger comes close to that).
To be serious again, I remember those floppy-disk-sending-times very well. I remember things like "We need a copy of the disk" and received a photocopy some days later. Rolling out an update was a tremendous hassle. And so on ...
Best regards,
Tom
"Did I offend you?"
"No."
"Okay, give me a second chance."
Tom
"Did I offend you?"
"No."
"Okay, give me a second chance."
Re: eXpress++ Build 268 is released
Not only was handling of floppy disks a hassle, but printing documentation was a nightmare.
Dirk Lesko, the author of Funcky, was so frustrated with it that he bought a printing business to print his own manuals.
That elevated his frustration to an even higher level.
I recall asking him "Why would you want to go into the printing business when you are already in the best business there is - software?"
A year later, everyone was sending out documentation as Norton Guides. Problem solved.
On another note:
Yesterday, December 7, 2021, a date which will live in Infamy, Winner's Garage server was suddenly and deliberately attacked by a software program created by the Empire of Spyros Bobby Drakos.
Dirk Lesko, the author of Funcky, was so frustrated with it that he bought a printing business to print his own manuals.
That elevated his frustration to an even higher level.
I recall asking him "Why would you want to go into the printing business when you are already in the best business there is - software?"
A year later, everyone was sending out documentation as Norton Guides. Problem solved.
On another note:
Yesterday, December 7, 2021, a date which will live in Infamy, Winner's Garage server was suddenly and deliberately attacked by a software program created by the Empire of Spyros Bobby Drakos.
The eXpress train is coming - and it has more cars.
Re: eXpress++ Build 268 is released
Best regards,
Tom
"Did I offend you?"
"No."
"Okay, give me a second chance."
Tom
"Did I offend you?"
"No."
"Okay, give me a second chance."
-
- Posts: 481
- Joined: Wed Jan 27, 2010 10:25 pm
- Location: Berlin Germany
Re: eXpress++ Build 268 is released
Hello Roger,
the changes you made because of the color settings in _dcclass.prg will break existing code, the lEnable is not noticed anymore. So f.e. in DCSUBMENU all items are shown as they are selectable.
So i added (line 5809):
the changes you made because of the color settings in _dcclass.prg will break existing code, the lEnable is not noticed anymore. So f.e. in DCSUBMENU all items are shown as they are selectable.
So i added (line 5809):
Code: Select all
if .not. lEnabled
nColor := GraMakeRGBColor({180,180,180})
endif
_______________________
Best Regards
Wolfgang
Best Regards
Wolfgang
Re: eXpress++ Build 268 is released
Hello Wolfgang!
Can you completely post this function section so that I can understand that.
My lincounter is on another place
Can you completely post this function section so that I can understand that.
My lincounter is on another place
best regards
Hans
Hans
Re: eXpress++ Build 268 is released
Sorry, I am a little behind on this issue.
I will look into it today.
I will look into it today.
The eXpress train is coming - and it has more cars.
-
- Posts: 481
- Joined: Wed Jan 27, 2010 10:25 pm
- Location: Berlin Germany
Re: eXpress++ Build 268 is released
Hans, see post viewtopic.php?p=17411#p17411
_______________________
Best Regards
Wolfgang
Best Regards
Wolfgang
Re: eXpress++ Build 268 is released
i know this - but you say you put this 3 lines
in the code - what position ?
bevor "nColor := ::fgColor " or ....
Code: Select all
if .not. lEnabled
nColor := GraMakeRGBColor({180,180,180})
endif
Code: Select all
nColor := ::fgColor
IF Valtype(nColor) == 'A'
nColor := GraMakeRGBColor(nColor)
ENDIF
aDAttrs[GRA_AS_COLOR] := nColor
nColor := ::bgColor
IF Valtype(nColor) == 'A'
nColor := GraMakeRGBColor(nColor)
ENDIF
aDAttrs[GRA_AS_BACKCOLOR] := ::nColor
best regards
Hans
Hans