Good day -

We just updated an EL5 linux server to both ASHELL 6.5 and ATE 6.5. They started complaining about screen colors looking off and it seems that when we create a dialog using the AUI'BGC the colors are indeed off. It almost looks like the rbg values are reversed...then it occured to me that this sounded familiar.

Any ideas what would cause this? We are going to try to reinstall the bin on monday.

TIA.

(PS: I washed my hands before posting this question )

I always had hoped you did, Frank

Careful you two - we may need to close down all interactions on this forum if you can't maintain sufficient emotional/intellectual distance from each other!

As for the dialog colors, I do vaguely recall some issue we had with you a couple of years ago relating to how colors bled up through transparent layers of standard dialogs, MBF_DLGNOCAP dialogs, TAB controls, etc. But I thought that was resolved long ago. Are you suggesting this it the first time testing this combination of Linux / A-Shell / ATE and therefore the first opportunity for some systematic problem to be noticed? Or that it's peculiar to one server or one workstation? Or just plain intermittent?

Probably the best way to quantify the problem, would be if I could ATE in to a test server to see it live. Or, take a screen picture and combine it with the control dump showing the fgc/bcg colors for the relevant controls.

Hey Cap -

No, it's been working fine all along, including all latest flavors of ashell and ATE, just weird on this one server seems to be misbehaving. Thinking that the bin is the wrong flavor, or didn't install properly, going to reinstall today... will report back.

Ok we reloaded our 1662 el5 bin and no joy, so i patched it with the latest tz 1664.4 and it worked. SO there is something wrong with the 1662 el5 bin that you made for me a few mos ago apparently.

When you have some time perhaps you could compil a new 6.5 el5 bin and put it up on the /dist site so we have a clean one moving forward.

Not urgent, but necessary.

TIA

Well, considering that there have been over 50 individual .x updates or patches since 1662 (June 2019), it's certainly possible that something was fixed! I've been dragging my feet waiting for completion of some offsite beta testing of a couple of new features before posting a new build, but if that doesn't finish in another day or so, I'll back those out and get on with it.

That's fine, thanks. So there has been 50 minor patches between 1664 and 1662?? i didn't realize that was even possible! Perhaps some of these should have been major edit updates??!

Not between 1662 and 1664; between 1662 the current 1676.7. There are w32 and -el7 versions in the beta download directory if you want to try them out.

1662 was the latest tz available for the el5 variant.

You could interpret that as suggesting maybe it's time to move up to -el7 (considering the -el5 end of life cycle was Mar 2017)!
Or you could interpret it as being on the to-do list.

The advice to update your Linux notwithstanding, here's a 6.5.1676.7-el5 build package:

ash-6.5.1676.7-el5.bin
ash65notes.txt

If we trash canned every piece of software that ended it's intended life cycle i am sure most of us would be out looking for other lines of work...

Thanks for the update.