Sign in to follow this  
Followers 0
Lotus

Hub Name Bug

10 posts in this topic

If I add a hub to favorites and change his name to ABC on my favorites list, ApexDc displays ABC instead of what he receive in $HubName.

If I add a hub to favorites and his name is X and after a day the owner changes the hub name to Y, Apex still shows X instead of Y when I connect to the hub.

Share this post


Link to post
Share on other sites

If I add a hub to favorites and change his name to ABC on my favorites list, ApexDc displays ABC instead of what he receive in $HubName.

The name ABC is shown instead of the hub name. I *do not* see the hub name when I connect to the hub... When someone changes the topic, I *do not* see the topic... the title of the mainchat window is ABC... :unsure:

Share this post


Link to post
Share on other sites

There is a setting "Enable $HubTopic support" in the settings, try turning that on :unsure:

Share this post


Link to post
Share on other sites

There is a setting "Enable $HubTopic support" in the settings, try turning that on :crying:

Sometimes it seems so difficult to explain something as simple as that. But I assume this is partially because of my bad english.

Please note that I was not talking about $HubTopic. I was talking about $HubName.

When admin types !topic <new topic>, most of the hubsofts send $HubName to the users, not $HubTopic...

By the way, $HubTopic support is enabled and works fine.

Please make the following experience:

1. Press Ctrl+F to open favorite hub list.

2. Select the first hub.

3. Click Propreties.

4. Set the hub name to: "Lotus Is The Best"

5. Delete the eventually hub description also (!!!)

6. Click Ok.

7. Reconnect on that hub... :)

Share this post


Link to post
Share on other sites

Well, I don't know, everything seems to be okay here - I did the experiment you recomended.

Tested on Ynhub and Verlihub.

Share this post


Link to post
Share on other sites

He has an option enabled that triggers this behaviour... just can't remember where it was put in settings exactly.

Share this post


Link to post
Share on other sites

He has an option enabled that triggers this behaviour... just can't remember where it was put in settings exactly.

So, finally, we are getting somewhere...

You are correct. That option exists. And it has a bug... :)

The option is under Appearance tab and is called: "Hide Hub Topics".

But note that it is *disabled* in my client. So, being disabled, the topic should not be hidden... isn't it ? And everything should be and look normal... only it isn't.

If I enable that option, it works as expected. The hub name is correctly shown and the topic is hidden.

If I disable that option, apparently the topic is shown... until I change the hub name and description in favorite list.... :crying:

Mek: please disable that option and do that experiment again...

Crise: there is another option that I don't know about and is interfering with this ? If not, it is pretty clear to me that this is a bug... please check again carefully. Why if I disable that option the hub name is taken from the favorite list, instead of being taken from the string sent by the hub in $HubName ?

If you still can't figure out the problem, I will give you another hint:

1. Option "Hide hub topics" disabled - so topic should be seen.

2. Connect to a new hub.

3. Type /fav => the hub data is stored in favorite list.

4. Exit the hub and ask an operator from that hub to change the topic.

5. Reconnect the hub again.

The topic shown is NOT the new topic, but the one that was when you first connected to the hub... the old one... :)

Still thinking it is ok ? No kidding... :)

Suggestion: I might be wrong, but I think that the first $HubName sent by the hub (just after validating nick) is the hub name alone, with no topic appended. The second $HubName, however, contains the hub topic appended to it. If i am right than you could use that very easy to implement this feature correctly...

Share this post


Link to post
Share on other sites

"Hide hub topics" should have nothing to do with this. The option I was talking about is: "Use details in favorites to identify hubs"

Share this post


Link to post
Share on other sites

Found the setting.

Still, there is a small bug left.

When option "Hide Hub Topics" is checked, enabling "Use details in favorites to identify hubs" does not act as it sounds.

The hub name is still taken from the $HubName and not from the favorites list data, as expected.

Last experiment. Enable both options ("Hide Hub Topics" and "Use details in favorites to identify hubs".) Rename a hub in favorite list to "xyz" and reconnect. The name of the hub is still taken from $HubName and is not "xyz" as expected. (When "Hide hub topics" is unchecked, the name of the hub is indeed xyz as in favorite list).

I assume the bug is in the "hide hub topics" implementation: the code that is executed when this option is enabled does not take into account the other option with fav...

My apologies, however, the bug is much smaller then I thought and the tone of my voice was much louder then it should... :crying:

Share this post


Link to post
Share on other sites
Sign in to follow this  
Followers 0