Crise

Basically messages that are not useful, like the one mentioned... and then some kick messages if you are an OP then you are likely to get them in OP chat as anyways, so it's not really a drawback to turn it on. Regarding an offline guide, aside from the extremely outdated user guide in Guides section there aren't any at present... so wanna make one? :angry:

I already answered to one of your questions in that post I linked to... ie. that if it was possible to accurately detect the mode of the taskbar we would have made the tray behaviour adapt to that but it's not Microsoft does not provide an API to get the new taskbar settings programmatically, nor is there any well documented workarounds to do it. Also since there is no accurate way to detect the new settings then it only makes sense that we work for/with the default settings. Regarding "other apps are doing it" not being a valid argument... actually that was not my argument to begin with, I just used Windows Live Messenger as an example since it is commonly used application. Other apps are starting to do it, yes, but did you ever consider why? Because the whole idea of the taskbar changes in Win7 is that every app that has a presence on the desktop is in the taskbar and to have one place for launching and interacting with an application. What we call system tray is notifications area in Win7 hence most icons get hidden by default, when there are no notifications, thanks to windows (which actually means that users who don't change settings need more clicks to get to the tray icon than before). Also did you really read the changelog as I suggested... because if your did, the answer for all your questions lies in there: Change: Always minimises to taskbar in Windows 7 (Run in Compatibility mode if you want to revert) Same trick can be used with Windows Live Messenger afaik, in case you really want a tray icon for it as well btw. .

I can look into it, might be possible to work aeound it. As forr 6. There is an option somewhere that affects it, don't remember exactly but it's probably the "Filter kick and NMDC debug messages" in Appearance,

Did you read this part at all, changed it a bit to emphasize the point : In other words... the client regards any message without "<Nick> " at the begin as a message without a sender and hence treats it as a status message. The reason why it may have coincidentally worked in an earlier version is because the bahaviour regarding status messages was changed. The point, however, is that /me is not a standard part of NMDC, unlike it is in ADC... it was originally purely client side thing in NMDC. But then hubsofts started trying to be smart about it, unfortunately this was not unified smartness in that different hubsofts are "smart" in a different way (and some not at all, like ynhub f.ex. which still return the message as is, which is what the client expects). So it becomes difficult for the client to respond correctly on each different behaviour.

More detailed info on it in here: People, please at least read the changelog before you report a bug, thank you .

6. depends on your configuration as well... 1. Well the thing is, in NMDC some hubsofts send the /me message back as * Nick message, but the client does not expect the hubsoft to do this because in NMDC chat messages are supposed to be like <Nick> message. ie. normally a hubsoft in NMDC would be expected to return /me as <Nick> /me message... which is what the client expects, but some hubsofts try to be smart and do it differently and this makes the client behave differently.

Well there is a bug here but not the one you are expecting... ApexDC is not supposed to minimise to tray on Win7, at all . Because tray icons in windows 7 are primarily there for notifications.. ie. balloon popups and the like. If you look at other apps, say Windows Live Messenger no longer has tray icon at all with Win7 (we still have it since we use balloon popups, but since it is hidden by windows as default on Win7 it makes sense to change the minimise behavior to never minimize to tray on it). As far as saving space on screen goes, whether the app is in taskbar or in tray the difference is minimal especially with the new kind of taskbar of Win7 where even the taskbar buttons are more like icons by default. Yes, I know that can be changed... and if I could I would have adapted the minimize behaviour to take this into account, however, at present there is no way to do it (not at least a documented one). This is in other words an intentional change introduced by 1.3.1 for all Win7 and future systems. The bug that is there though is that it still minimizes to tray on Win7 at app start if minimize on startup is on.

Probably this is caused by stupid mistake on my side... should be fixed in next release.

We have also changed the archive format we use to release files to the 7zip format (7-zip is free open source multi-format file archiver) for much better compression. But have no fear, if you used WinRAR to open our files before it should still be able to do the job for you just fine. However, if you were using WinRAR or some other archive utility, and feel like trying something new... since 7-zip is free and open source. We recommend you to give it a try, you stand nothing to loose .

Well hopefully at least some of these issues have been resolved now...

It varies depending on the window background color you use (ie. it is calculated dynamically from it). It is possible, however, to get almost any alternate color on practically white background though if you play with the window color a bit (I say practically white because it's not 100% white nut if done right human eye can not make out the difference).

Not new, Mek, next... for a little while longer anyways .

The use a client to do the job... that can be done easily.

Two colors is already possible... there is a check box for it in appearance. So is resizing the message field, or rather it adapts to the entered text if you change the setting for it in experts only if I remember correctly.

Read change log for StrongDC 2.40 ^_^

What Big Muscle was trying to say, although in the tiniest of fonts, is the third sentence in his post. To put the same in other words would be: It is an issue with Apex 1.3.0, it is known already, and it will be fixed in next release. Thanks for your report in any case. However, you should not share installed programs (or raw dumps of some installation files), which seems to be the case in your example. Share a disk image or whatever instead. Because quite frankly most OP's I know would kick you for sharing stuff like your example... most probably with reason "don't share installed files" (or something similar). That being said ApexDC does in no way support illegal sharing of copyrighted content, like in your example, and thus can not be held responsible in any way... blah blah blah (you know how that continues ).

Finally someone is offering to do, what I should have done years ago... :)

Those two menu items work differently that's why...

There is a way, well to be more precise the background image is not applied to the richedit but rather what's behind it (ie. the window or another control that supports painting events) then the edit control's opacity is adjusted somehow I assume. I have not tested this theory, as of yet, but it could be doable. Edit: Quick Google search came up with this: http://www.codeproject.com/KB/edit/SemiRichEdit.aspx

Hardly a big mistake... mistake maybe, but not a big one considering several alternate solutions have been given in this topic already.

You can do that by setting the colors you don't want to see to the same color as your "General Text" in chat styles.

It might be over the top but looking at the client selection in various public DC hubs... you wouldn't believe how many people deem to never upgrade their client. While I can't do anything to get those users insisting on using oDC etc. to upgrade, at least I can make staying on old versions of Apex little more difficult to the average user. Yes, only a little more difficult. And to prove that there are still users running versions like 0.4.0 or 0.2.2 of Apex.. as well as the very buggy beta versions of 1.0.0 (which is something that I do not understand at all, the bugs in those versions should be getting users to upgrade, but no). Despite all the measures we have taken to get people to upgrade. To put it in other words. I have been in DC long enough to know that it's almost an exception rather than a rule for someone to actually upgrade their DC client (basically it only happens when a hub the user happens to go to suddenly says that clients older than x are no longer permitted, that is assuming the user thinks the hub is good enough to upgrade his client for). Edit: and yes in theory I am all for letting the users make the choice between client versions... and if the number of people on outdated versions was less than it is, I probably wouldn't mind as much. But since that is not the case, and since DC is not just one persons sandbox...

You know, that is probably not even true about 1.3.0 being buggier than 1.2.2... 1.3.0 has countless bug fixes (many from StrongDC merges, but that is irrelevant), it just so happens that the new bugs in 1.3.0 are more visible in every day use than the ones you had on 1.2.2. What I am trying to say is that there will always be bugs... some more severe than others. And in terms of severe bugs, 1.3.0 has about one or two of those to my count (the xml nesting depth issue, and certain plugin related bug), I acknowledge that some of the other bugs in 1.3.0 might be annoying... and that's why we are working on 1.3.1 as fast as we can manage. But if we work on it too fast then people will start saying: "This bug was in 1.3.0, why isn't it fixed in 1.3.1" We could have pushed out an update the day after 1.3.0 had been released to include the few fixes we were missing from StrongDC 2.40, but we did not do that because we knew that there are also other bugs that needed to be addressed from our own changes. Sure you can say that we should have done more throughout beta testing... but in regards to that we have limited resources and time. It also did not help that that some of the less severe bugs in 1.3.0 are on areas which are not used by everyone. Also remember that ApexDC is a freeware open source project, so we have no obligations to anybody, nor does any of you have any obligations to us. You dislike the way we do things then there is always the other choice.

Yeah name is saved in strong... because we miss few last fixes fro SDC 2.40, 1.3.1 will address this.

Aoex has had kept that option around for far longer than SDC, BM removed it way back when StrongDC 1.00 RCX became StrongDC 2.xx... Have you ever thought that there might be a reason for why he removed it? We just happened to keep the option in there for a bit longer (same thing applies to Get IP Address button which is still there). Our reasons are not purely cosmetic though... the "Update IP on DHT firewall check" does overlap with the old "Update IP on startup" you see.