Greg

Member
  • Content count

    1132
  • Joined

  • Last visited

Posts posted by Greg


  1. Hey,

    i'am also trying to emulate Apex under Wine.

    I read some posts and installed Apex without emoticons, turned of the progressbars, an nearly everthing that i found in the Apex Settings :thumbsup:

    I can start Apex and connect to my hubs.

    But when I start a download oder somebody starts an upload, Apex crashes with the following exception:

    I also read about turning of the tooltips but couldn't find an option to turn of these.

    My Wine-Log contains this information:

    Can you explain me what I did wrong?

    Thanks

    Max

    Which version of ApexDC++ are you using? We don't officially support WINE at all, but 0.4 happens to work under it. If you're using a more recent version then it's quite possible it just doesn't work under WINE. There's not much we can really do about it, if that's the case, to be honest.


  2. The bug concerns nick copying/sending public messages.

    How to see:

    1) rightclick any nick in Chat and do "Copy nick".

    2) rightclick another user in the userlist and do "Send public message".

    You'll see that first nick (that was copied in the 1st step) was placed in msg window, but, of course, message should be addressed to the second one.

    PS. I've asked to test my friends this on StrongDC 2.12 -- they have the same result.

    Maybe this is a feature... but then it's a strange one :unsure:

    I would assume it's a bug, but not one that should be a priority to fix. This should be reported to SDC, if it hasn't already, and then if/when it gets fixed we can just merge that into ApexDC++. :)


  3. a bit tricky to explain...

    here is what happens... assume 1 user is on 3 same hubs as you are

    now when he tries to grab your list, apex seems to open additional upload slots and in the end you have the same user downloading your filelist from three different hubs and there is nothing you can do about it.

    tried to close two of those connections, no result.

    same sh-- after a few second.

    now, is there no way to prevent these sort of things hapening?

    can't apex detect that it is uploading 3 filelists to the same IP and close all but one connection automatically?

    speaking of small upload slots... why is the minimum set to "3".

    The NMDC protocol doesn't have have a way of uniquely identifying users, but as Satan says the ADC protocol will, which we should see gradually getting phased in. Basically, this isn't a bug, just an inherent limitation of the protocol. As such I'll move this topic to Support, but it's something which has been discussed before, you should be able to find some threads in the Support forum, and probably the Feature Requests forum.

    I don't know what you're asking about the small upload slots though. What's wrong with a minimum of three?


  4. Perhaps make a plugin that gives stats to a vista gadget is that a good or bad idea ?

    Vista Gadget API

    If it's within the scope of what the Apex plugin API can do then yes it's worth doing, if only as an example plug-in for people wanting to use the API. I don't know if it would be too confusing as an example plug-in due to having to deal with the whole VIsta sidebar API. I'm not a developer, so I guess I don't know what I'm talking about, but we should have a sample plug-in.


  5. It's not a bug that needs fixing....

    Indeed, it's just a potential feature we don't have, as a perfectly acceptable solution as mentioned above is available. If you want to request this feature then try searching the Feature Requests forum for it, and if no such topic exists about it then feel free to create one. This feature will not be added really soon even if it does get added to the todo list, so using a DynDNS account is the simplist solution to your problem.


  6. Don't get me wrong guys, once Vista gets to a stage where it isn't riddled with bugs, by all means, work with it, but at mo, it's buggy! :)

    It's buggy? There's only one bug I know of that affects me, and that's arguably not Vista's fault. (My Computer won't sleep properly - but this should be fixable with a BIOS update.)


  7. Minimum share size is an option/decision for hub owners. You you feel people who are not sharing enough are downloading from you then either contact the hub owner or leave and join a different hub. We have no idea of letting individual users set this option themselves, it would almost certain result in this client being labeled as a leecher client, and with good reason, it would be a feature that would almost certainly get abused. What you think is a fair amount for people to share differs to what other people is a fair amount, I don't think letting everyone self impose their own limits wouldn't work. These decisions should be left up to the hub owner.

    Closed. (PM me if you have a problem with this.)


  8. If you don't like the way we handle the usage of the beta software which is released (purely so people can test it and help us fix bugs for next version), then don't use them. Revert back to 0.4 or be prepared to follow the path to the next stable version, as we see fit. Any version which we do not consider stable should be phased out if bugs in them are fixed. What is it that changed in Beta 5 that people dislike?