Avast WEBforum

Consumer Products => Avast Free Antivirus / Premium Security (legacy Pro Antivirus, Internet Security, Premier) => Topic started by: Technodrome on June 09, 2004, 08:34:50 PM

Title: avast! GUI bug?
Post by: Technodrome on June 09, 2004, 08:34:50 PM
Hi All,

Sorry if this is a repost. I couldn't find any info on this.

I am not able to see information or properties for a specific file within information window(EUI). When I click on file properties it takes me to task settings.

 

Title: Re:avast! GUI bug?
Post by: Technodrome on June 09, 2004, 08:35:15 PM
and
Title: Re:avast! GUI bug?
Post by: Lisandro on June 09, 2004, 08:58:32 PM
I haven't noticed that but you are fully right  :-\ Seems a bug that is still present at the 4.1.407 Beta version.
Title: Re:avast! GUI bug?
Post by: Technodrome on June 09, 2004, 09:11:56 PM
Hopefully someone from Alwil (Vlk or Igor) will see this and fix it before they release 407 build.  8)


tECHNODROME
Title: Re:avast! GUI bug?
Post by: igor on June 09, 2004, 10:01:30 PM
Well, I will have to ask because I'm not sure if it's a bug or feature.
It's possible that the item Properties should actually show the properties of the corresponding Task (which is what it's doing), not of the file.
Title: Re:avast! GUI bug?
Post by: Lisandro on June 09, 2004, 10:10:05 PM
Well, I will have to ask because I'm not sure if it's a bug or feature.
It's possible that the item Properties should actually show the properties of the corresponding Task (which is what it's doing), not of the file.

Suggestion: change Properties to Task info  8)
Title: Re:avast! GUI bug?
Post by: MikeBCda on June 10, 2004, 12:30:05 AM
Unfortunately that's one of the problems with Win (just about any semi-recent version) -- "Properties" is a be-all and do-all term that, more often than not, isn't particularly context-sensitive.

Or, as in this case, there's considerable confusion between Win and the user as to what the context really is, or is supposed to be.
Title: Re:avast! GUI bug?
Post by: Vlk on June 10, 2004, 10:27:20 PM
btw this should be fixed in the latest release build (4.1.412). thanks to everyone involved. ;)