New Version issue

[colweb]

Hi, been using the Beta V6 for a few weeks (or is it months?) and found it very usefull.

However I noticed something with the new version, I can no longer open up a user's memberships and double click a group to see its properties.

Something to add back in? :P

[cmccullough]

Re: New Version issue

I don't remember anything like this. Can you give us a step-by-step on how you did this before?

[colweb]

Re: New Version issue

No problems.

In the beta, double click a user. "Members of" tab, double click a group, you get the group properties. Then if you wish, you can double click a user in that group and so on and so forth.

In the new version the double click doesnt work atall. Doh doh doh

[colweb]

Re: New Version issue

Oooops!

Just tried it again and got the old "serious error, send a report" thing.

I tried it by listing all users in a 2000 domain and double clicked a random user, then tried to open the Domain Users group...

[kstanush]

Re: New Version issue

I'll look into this and get back to you. Thanks for reporting this problem.

[kstanush]

Re: New Version issue

This is a bug, which will be fixed in rev 'C'. This revision should be available either by the end of the week or early next week. We are trying to get as many non-critical bug fixes as possible into this revision.

Thanks for reporting this problem. If something that you are doing requires an immediate fix to this, let us know.

[colweb]

Re: New Version issue

Great fix guys, works lovely in Rev C.

However it doesnt work somewhere else, slightly different.

Open a server, view local groups - see domain groups in the Admin group for example, double click that group and nothing happens.

Its handy if this opens the global groups properties so we can audit access quicker, but not essential (I could write the group name down then go searching....)

:P

[kstanush]

Re: New Version issue

If I understand this right, this behavior has never been implemented. Local groups on servers use Hyena's own property sheet. This is a popular feature request, however.

Thanks for letting us know that the fix worked.