X-Fusion
Historical / Guest
Like I tell everyone else that uses Nicklust, revert to nicklist.dll. I don't care about limited possibilities, there isnt enough documentation for people who are just now starting with nicklust to learn off of. I used nicklust when it first came out, and I've been working with it, and it's by far one of the hardest dlls to play with due to constant callbacks and markings. So, try nicklist.dll and see where that gets you.
X-Fusion
Historical / Guest
It misses you to Fahad <3
Travis
Historical / Guest
dll nicklust.dll Mark $window(#).hwnd <name> rowselect tooltips balloontips hideempty hottrack underlinehot staticedge
take a look at your Mark code.
X-Fusion
Historical / Guest
It's not as easy as that, you MUST call back every channel you preform that action on.
Travis
Historical / Guest
All you have provided so far are jokes, doubts and the suggestion to not use Nicklust.dll. If you don't know the answer don't respond to his help request. I'm trying to work with the guy.
X-Fusion
Historical / Guest
Uh, excuse me? I've worked with nicklust for awhile, and I'm pretty sure its not as easy as 'marking' the channel. You DO realize you have to callback every channel to return the desired information, right?
X-Fusion
Historical / Guest
It's harder for people that are just starting to use dlls, or don't know the inner workings of nicklist or nicklust. Nicklist dll is almost the same as nicklust, but, doesnt require nearly as much work for it imho. Opinions are opinions I suppose.
X-Fusion
Historical / Guest
Thats a nice nicklist. Maybe I could have worded my first statement better. I tell people to go revert to Nicklist because it's probably the easier of the two dlls to learn off of. Once you learn that, nicklust should be a breeze. If you start with nicklust first, you'll have to figure out callbacks, markings, etc. If you play with Nicklist, you'll figure out how to do most of that. Anyway, good luck.