Seems like ClickToFront commodity is not working since the last OS update via AmiUpdate.

Anybody else have this issue, or is it just me?

@amigadad

Yup, lots of people. Already reported to the development team.

_________________

@djrikki

OK, thanks!

@amigadad

I was certain mine was ignoring me. Time for a roll back.

Interesting, I guess it's a small blessing that I'm one of those people who had issues with the version of AmiUpdate in Update 6 crashing, and therefore haven't updated anything else since. If ClickToFront wasn't working I'd find it immensely annoying!

Last edited by Daedalus on 14-Feb-2013 at 09:55 AM.

_________________
RobTheNerd.com | InstallerGen | SMBMounter | Atoms-X

@amigadad

Same here too.. I was blaming my mouse!

@amigadad

Known issue, and already fixed - we just need to wait until the updated ClickToFront becomes available via AmiUpdate.

_________________
The Rear Window blog

AmigaOne X5000/020 @ 2GHz / 4GB RAM / Radeon RX 560 / ESI Juli@ / AmigaOS 4.1 Final Edition
SAM440ep-flex @ 667MHz / 1GB RAM / Radeon 9250 / AmigaOS 4.1 Final Edition

@Daedalus

I found the AmiUpdate in Update 6 to be fine. Just don't update it! Update the system components first, reboot, then update AmiUpdate. That works for ne.

2.32 works in Update 5, crashes in Update 6, but works again in an Updated 6.

@Hypex

Thanks, I'll give it a go at some stage when I have the time / motivation

_________________
RobTheNerd.com | InstallerGen | SMBMounter | Atoms-X

so you need to work out what versions of systems components work reliably and stick to them while you need to prevent an update tool from updating itself? wow..

@Daedalus

Quote:

Interesting, I guess it's a small blessing that I'm one of those people who had issues with the version of AmiUpdate in Update 6 crashing, and therefore haven't updated anything else since. If ClickToFront wasn't working I'd find it immensely annoying!

AmiUpdate 2.32 requires Libs:update.library v53.11. You are welcome to stay at update 5 forever if you like. The rollback feature is very easy to use if you spot a problem. The whole point of the new update system is to get a fix out the door fast instead of waiting for a major update archive that could take months.

We all use our systems in different ways, in most cases, bugs just don't show themselves easy. Some ppl just like to bitch, others like to jump in & help improve the system, the choice is yours.

_________________
Hate tends to make you look stupid...

@wawa

Quote:

so you need to work out what versions of systems components work reliably and stick to them while you need to prevent an update tool from updating itself? wow..

Says the expert who's never used the system....

Leave crap statements like this for moo.

_________________
Hate tends to make you look stupid...

@sundown

Thanks, I'm well aware of the importance and intended functionality of the update, however you should also appreciate that there was no way that I could find to get it working without having to roll back and start trying to find specific versions of libraries to install by hand. And at the moment I have far more important things to be doing than that. I guess I'd just like to wait until a fixed version is released that I can jump straight to without having to mess with something that, of all things, should "just work".

Like I said, maybe some day I'll have a few hours to spare and I'll sort it by hand, but for now I'll stay with my perfectly working (for me) update 5.

@wawa

Nice to see your level of maturity hasn't changed. Do you not get the attention you crave from Amiga.org and Moo?

_________________
RobTheNerd.com | InstallerGen | SMBMounter | Atoms-X

@sundown

Quote:

Leave crap statements like this for moo.

this wasnt a statement because it ended with question mark, you know. and im not posting on moo.

@sundown

Quote:

The whole point of the new update system is to get a fix out the door fast

That's what they claimed. But apparently, the whole point is to release untested updates to paying customers and wait for feedback.

Seriously, there's either not a single betatester using ClickToFront (which seems unlikely, given the amount of actual users having it installed) or it simply got released straight after being compiled. And we all know this is not the first incident of this kind.

I don't have a problem with skipping proper testing - they're lacking betatesters as much as they are lacking developers. I'd just appreciate if it would be communicated as such, instead of claiming this approach would somehow speed up development and/or code quality magically.

Quote:

Leave crap statements like this for moo.

Very constructive attitude. I'm sure all of OS4's problems will go away if wawa stops posting. That's how it works, right?

@cgutjahr

actually good part of this update practice is that people like karlos and other non core contributors are able to get their fixes, like those p96 and warp libs updates are i suppose, out of the door. os4 releases are now a bit comparable with aros nightlies, which actually is not that bad, speaking from a perspective of a frequent aros68k tester.

@cgutjahr

Quote:

That's what they claimed. But apparently, the whole point is to release untested updates to paying customers and wait for feedback. Seriously, there's either not a single betatester using ClickToFront (which seems unlikely, given the amount of actual users having it installed) or it simply got released straight after being compiled.

That's absolutely not what you can infer from this little glitch. In fact you have absolutely no idea how the process is going on under the hood. All you can do at best is doing supposition (which by the way are based on *no* fact nor any knowledge that can support your ideas).
The continuous update cycle is still relatively young it probably still needs some adjustments. But it was generally well received *by the actual users of the system* especially because you don't need to wait too long to obtain a specific fix.

Quote:

And we all know this is not the first incident of this kind.

Ah and which other incident do you have in mind?

_________________
AOS 4.1 : I dream it, Hyperion did it !
Now dreaming AOS 4.2...
Thank you to all devs involved for this great job !

@cgutjahr

Quote:

Seriously, there's either not a single betatester using ClickToFront (which seems unlikely, given the amount of actual users having it installed) or it simply got released straight after being compiled. And we all know this is not the first incident of this kind.

Kas1e tried to explain the situation in the Hyperion forums. The betatesters already had installed a fixed version of ClickToFront in their systems before the Intuition and IPrefs updates were available to them. Apparently, when the said updates were under betatest, everybody forgot about the little commodity, and nobody tried testing the updates with the original ClickToFront.

So in the end: yes, an untested component has leaked. Awkward, but it does not challenge the whole idea and purpose of AmiUpdate.

_________________
The Rear Window blog

AmigaOne X5000/020 @ 2GHz / 4GB RAM / Radeon RX 560 / ESI Juli@ / AmigaOS 4.1 Final Edition
SAM440ep-flex @ 667MHz / 1GB RAM / Radeon 9250 / AmigaOS 4.1 Final Edition

@cgutjahr

Quote:

Very constructive attitude. I'm sure all of OS4's problems will go away if wawa stops posting. That's how it works, right?

Nope, but comments like wawa's are hardly likely to help fix it, either. And while your comment is fine, there's a tone about wawa's "contributions" which suggests plain trolling.

_________________
RobTheNerd.com | InstallerGen | SMBMounter | Atoms-X

@cgutjahr

Quote:

That's what they claimed. But apparently, the whole point is to release untested updates to paying customers and wait for feedback.

No this was simply a f*** **
Quote:

Seriously, there's either not a single betatester using ClickToFront (which seems unlikely, given the amount of actual users having it installed) or it simply got released straight after being compiled. And we all know this is not the first incident of this kind.

Click To Front had been extensivley tested, it just got left out of the update, which is decidely embarassing and abit of face palm / doh moment.
Another issue popped up in the mean time which needs fixing / is fixed.

The most likely reason the omission was overlooked is that we test the updates process against a clean system and ClickToFront is in active by default.

Quote:

I don't have a problem with skipping proper testing - they're lacking betatesters as much as they are lacking developers. I'd just appreciate if it would be communicated as such, instead of claiming this approach would somehow speed up development and/or code quality magically.

The approach enables the deliverty of bug fixes and minor updates somewhat faster than before (things have been fixed that would previously have waited till the next major update).

Clearly it's not perfect but the same process can be used to fix the situation.

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad