Finally Logos Fixes Version 5. Thank you Logos!!

I only found this secret new feature (I hope Accordance isn't reading this!!) when (1) once again the layout saver can't remember the state on the RI ribbon and (2) the new active layout routine (I assume) won't allow moving the panel boundaries on any of my 5 windows after I've tried to fiddle with the RI ribbon's bad-boy behavior.

The above is after a Logos5 load while another software loaded faster (leaving a third piece of software showing below .... beloved Libronix of course). Obviously Logos5 doesn't do a repaint to account for its slow load times.

Same thing happens on the layout menuing.

Find more posts tagged with

Comments

JT (alabama24)

That is an AWESOME new feature! Thanks for sharing. [:P]

Rosie Perera

Sarcasm in subject lines is funny, but isn't likely to get your bug report noticed by Logos employees perusing the forum for same. Although they might perk up and want to read such a post of apparent gratitude, it's not guaranteed if they're truly busy and just looking for bug reports. Just a thought...

DMB

https://community.logos.com/discussion/comment/475310#Comment_475310

Rosie, if I remember right, you code. Logos4 and now Logos5 has a fairly high number of 'only in Logos' errors. Something's wrong with the coding process. And judging from their hiring, they're aware of quality control (though I don't know if that's coding or resources). But this is just one of many unique behaviors in Logos5 (many carrying over from Logos4). I've long ago learned to enjoy them. The one where if I minimize the last software window, a random Logos5 window will guaranteed pop open on its own .... that's been around since Logos4 rollout ... and merits a 'Good girl!!'.

The problem with these types of errors, is they're generally not reproducable on-order, they're typically not frequent, and absent serious squeeling, they're worth a yawn. So the problem is heavily dependent on good coding at the start.

The same principle exists for resource typos. Once the resource is released and thousands follow, trying to keep up is impossible. The mystery on the latter, is that most users can easily see (1) no basic spell checking (eg scanning for common errors, in light of multiple abbreviations) and (2) it's being scanned in by someone.

And indeed I've yet to find a 32bit application running on my W7/64 that has Libronix problems. Or Win95 software (running in my XP window) that has Logos 3D map problems. It's a pattern.

Rosie Perera

https://community.logos.com/discussion/comment/475327#Comment_475327

Rosie, if I remember right, you code. Logos4 and now Logos5 has a fairly high number of 'only in Logos' errors. Something's wrong with the coding process.

I totally agree!

I was merely poking fun at your choice of a subject line which will only amuse people like me and won't likely get your complaint listened to by Logos. Not that a single complaint about it could really fix the underlying problem which is a bad attitude towards code quality from the top of the organization down. They need to read and study this book by my former colleague at Microsoft, which is just about to come out in a vastly updated second edition: Writing Solid Code. In fact Steve just posted photos of the print-run on Facebook today, so it should be available RSN ("real soon now").

Dave Hooton

https://community.logos.com/discussion/comment/475622#Comment_475622

Not that a single complaint about it could really fix the underlying problem which is a bad attitude towards code quality from the top of the organization down.

A senior Software Manager had little time for Quality - "sorry, but that sounds like it will detract from the essential work that has to go on around here". After about one year of fire-fighting the "essential" work he was replaced by a Manager who fully embraced Quality and never had to worry about fire-fights nor badly slipping schedules. It wasn't that the project didn't require quality standards; just that one person's attitude & results.

Randy W. Sims

https://community.logos.com/discussion/comment/475622#Comment_475622

They need to read and study this book by my former colleague at Microsoft, which is just about to come out in a vastly updated second edition: Writing Solid Code.

Great book! As I remember it came out about the same time as Code Complete (by the other Steve). Read them both when they first came out and then again after. Excellent books. I hadn't heard about the new edition. I will look forward to that.