PureBasic Forums - English

Is it possible to have the complete source code of xlist, I do not use the libs because it is difficult to maintain compatibility with different versions of PureBasic ...

Thanks

Shopping around for source codes? I probably wouldn't be so suspicious if you hadn't immediately asked for srod's esgrid source as well. Source code for xList isn't available (yet) but your requests definitely make me raise my eyebrows.

Xombie wrote:Shopping around for source codes? I probably wouldn't be so suspicious if you hadn't immediately asked for srod's esgrid source as well. Source code for xList isn't available (yet) but your requests definitely make me raise my eyebrows.

If it is a problem, keep your code. I do not libs not to be blocked later in a project, if it's free and without support, I think it's loqique that source code is available, no need to be paranoid at this level, this is not secret defense is not it , I hope that the translation will be good ...

It's not a problem. Just bugged me momentarily. You'll have to wait a little while longer until I'm satisfied with it before I release the code. I will release it but just not yet. Sorry about that.

Xombie wrote:It's not a problem. Just bugged me momentarily. You'll have to wait a little while longer until I'm satisfied with it before I release the code. I will release it but just not yet. Sorry about that.

Okay, in this case I understand, in any case, I always respected the license for authors, if there are any limitations I seek an alternative programs or I lack the function that myself, but all this takes time and I do not think reinventing the wheel is useful ...

Updated the code with some fixes as well as to test whether I could freeze columns - for PurePi.

This version changes the xListPrepareRows function and I've included a new example that shows how to use it. The new example uses an ODBC connection to load in a SQL statement so you can see how this works. It's ugly since there are some limitations in select exact rows and columns and getting a row count but you'll get the idea.

To freeze columns you use...
And this will freeze all columns to the left of (and including) column #List_Column_ID_03.

Remove the frozen columns by sending column ID -1.

This was a quick patch up so anyone that is interested in this functionality will need to test it. Buttons "Test" and "Test 2" show how this is used in the "Test-ODBC.pb" example file included in the zip file.

Download: http://www.seijin.net/xList/xList.zip

I`ve tested the new "freezing feature".
I didn`t recognize any problem (GREAT Job , Xombie).
I`m thinking about using the XLIST object in my application(s).
Before deciding this, I have a few questions @Xombie:

1.) Is XLIST realy "complete handdrawn", or do you use a standard windows object like a ListView or a DataGrid as a base ?

2.) Do you have an actual overview about the functions (and their parameters) availible ?

3.) What is you current timetable to make the source of XLIST availible ?

Once more, you did a great job with XLIST and you could be proud of yourself.

regards
Bernd

1. 100% completely hand drawn. There are no controls behind it. It's an image gadget that I draw everything into.

2. Not yet

3. There are some big hurdles I need to accomplish at my job that keeps me from putting in more time on xList. I'm going to try and target February for a code release. If you're holding off because you're worried that I won't ever release the code then you don't have to worry. There are some bugs that need to be fixed and a couple more features I want to add into it before I do that.

Thanks for quick reply.
It`s not so urgent for me, so I think the best way for me is to wait until you`ll release the final version of XLIST.
In between I`ll use my workaround (keeping 2 ListIcons in sync),
posted in German forum:

http://www.purebasic.fr/german/viewtopic.php?t=18241

The problem decribed there is already fixed .

regards
Bernd

Good morning!

Some bug fixes and this version works with PB 4.31. The major change is that it allows for multi-line text as shown in the example.



This will only work with String type columns and (at the moment) text must be manually broken using CHR(13). Please note that it's only chr(13) and not chr(13)+chr(10).

DOWNLOAD HERE

This is enabled per-column and is set in the column property before you add the column. Like...
I'll work on something that breaks up the line automatically (I've added a 'BreakLines' option but it doesn't do anything yet) but that'll be down the road.

Please test and let me know if this works out.

EDIT: Forgot to mention that I've also enabled the Excel export option when you right-click in the very top-left corner of the list. This requires Excel and COMate to be installed but the program should hopefully work whether you have them installed or not. It should just disable the option.

EDIT2: Seems like sorting on multi-line text loses the row height so I'm working on that now.

I have a new version (DOWNLOAD HERE).

1. Lines can now be broken up automatically (see the images below) based on the length of the line and the column width. Add the \BreakLines = #True option to the column when you're adding it.
2. Height should stick when sorting.

The column width is small when the program originally starts up. xList does its best to fit the text within the column.


When the column is resized, the text fits to the new width.

This looks very neat indeed, I get an error that #Byte is already declared with a different value (you have a comment there that says as much too), do I just comment those out? Or is there some compiler option I am missing?

I don't think there's a compiler option. Are you using the basic test3.pb example?

#Byte was the constant from 4.20, I believe.

Yes, I tried the example, but the error is within the include.

#Byte is already declared with a different value.

I guess I can just comment out and offset the new ones. I'll try that.

Did that work out? I also noticed that I still don't have the line break stuff working 100% and I'll need to redo how I scroll vertically in case of really large multi-line rows.