The Single or Stand-alone table (part 4)

 Welcome Back!

Hopefully you are hanging in there. I know this is a lot of information to absorb. As we move forward things will begin to click. I'm going to skip over the ListView Gadget as it is identical to the ComboBox except that instead of ComboBox were using the ListView Gadget instead. I'll go ahead and post the code for you to review, but then we'll move onto the ListIconView Gadget.


  Procedure LoadListViewName(lvData.i)
    Protected DBID, Sql$ 
      ClearGadgeItems(lvData)
      DBID = DB::Open(DBTYPE::#Sqlite)
      Sql$ = " Select "
      Sql$ = Sql$ + " ID, "
      Sql$ = Sql$ + " Name "
      Sql$ = Sql$ + " FROM "
      Sql$ = Sql$ + " FighterSize "
      Sql$ = Sql$ + " ORDER BY "
      Sql$ = Sql$ + " Name "

      If DB::Query(DBID, Sql$)
        While NextDatabaseRow(DBID)
          AddGadgetItem(lvData, -1, GetDatabaseString(DBID,DatabaseColumnIndex(DBID,"Name")))
          SetGadgetItemData(lvData, ComboBoxEx::CountItems(lvData)-1, GetDatabaseLong(DBID, DatabaseColumnIndex(DBID,"ID")))
        Wend
      EndIf
      DB::Close(DBID)
  EndProcedure

Now we will turn our attention to the ListIconView Load. In my development it is very rare for a table not to have a ListIconView Gadget.  In my design/development process I design my screens First.  As I think through the flow of the4 screens I find I hit about 80% of the fields I eventually end up with.  So, knowing this ahead of time I never try and build in the columns of the ListIconView, I know it will always change.  I put the columns into the ListIconView here in the Module.

As before I do not use the "standard" PureBasic ListIconView Gadget, Once again favoring Thorsten Hoeppner's custom ListEx Gadget instead.

Let's begin the code review of the ListIconView; Below is the entire Code block for your review.  As before, I'll walk my way through this below.


  Procedure LoadListIcon(liData.i)
    Protected DBID, Sql$ 
    Protected Result 
      DBID = DB::Open(DBTYPE::#Sqlite)
      ListEx::DisableReDraw(liData, #True) 
      ListEx::ClearItems(liData)
      ListEx::RemoveColumn(liData, 0) ;Name
      ;===== Build Column Titles =====-
      ListEx::AddColumn(liData, 0, "Name", 60)
      ListEx::SetColumnAttribute(liData, 0, ListEx::#Align,  ListEx::#Left)

      Sql$ = " Select "
      Sql$ = Sql$ + "Name, "
      Sql$ = Sql$ + "ID "
      Sql$ = Sql$ + "FROM "
      Sql$ = Sql$ + "FighterSize "
      Sql$ = Sql$ + "ORDER BY "
      Sql$ = Sql$ + "Name "
      ;===== Populate Data Into Column =====
      Result = DB::Query(DBID, Sql$)
      If Result > 0
        While NextDatabaseRow(DBID)
          ListEx::AddItem(liData, -1,GetDatabaseString(DBID, DatabaseColumnIndex(DBID,"Name")) + #LF$ ) 
          ListEx::SetItemData(liData, ListEx::CountItems(liData) -1 , GetDatabaseLong(DBID, DatabaseColumnIndex(DBID,"ID")) ) 
        Wend
      EndIf
      DB::Close(DBID)
      ListEx::DisableReDraw(liData, #False) 
  EndProcedure

As we have seen before the Procedure constructor receives in the Handle of the ListIconView Gadget.   I then make the call to our DB Module to Open the database.  The next steps are to clear Rows and columns of the Gadget, then we build the desired columns, set each column's alignment and size.  

Then we build out SQL Query and calling our DB Module again Execute the query against the database.

Next, we iterate through the resulting record set and load the ListIconView with the necessary fields, separated by #LF$, from our query.

Finally, we once again call our DB Module to Close our Database.


Comments

Post a Comment

Popular posts from this blog

How to build this without writing Code

I'm not sure if I should do this now, because I have not explained a number of additional aspects to the code, but for those of you who are interested.  The foundation of what I shown you here, IS the foundation of code my PBXClassBuilder-Standard generates for you.  And I truly mean generates  for you. You can have all this code generated for you without writing a single line of it yourself. Now PBXClassBuilder-Standard is not perfect, it is approximately 90=95% accurate. And I am constantly tweaking it edging this number ever higher. To use PBXClassBuilder-Standard, You should start with Forms already laid out and built.  Within PBXClassBuilder-Standard you use intuitive screens to define your table structure, while linking the Table Fields to their intended form Fields.  Then link the Tables together as Parent Child, and finally you simply click buttons to generate the code, Including the SQL Code to create the tables. The Whole development process, post For...
Read more

Connecting the Forms to the Data-Layer (part 9)

Here is the whole View Code Sheet Define quitfrmSolarSystem Declare SolarSystemCustom() Declare SolarSystemSetScreen() Declare SolarSystemCreate() Declare SolarSystemModify() Declare SolarSystemDelete() Declare SolarSystemSetData() Declare SolarSystemSave() Declare SolarSystemClose() Procedure SolarSystemSetScreen() Protected String$, x, y, w, h, i, ID Shared WorkSolarSystem Protected EventID, MenuID, GadgetID, WindowID, Index Shared quitfrmSolarSystem quitfrmSolarSystem = #False If Window_frmSolarSystem() SolarSystemCustom() SetActiveWindow(#Window_frmSolarSystem) ;Set Screen Data SetGadgetText(#Gadget_frmSolarSystem_txtName, WorkSolarSystem\Name) SetGadgetText(#Gadget_frmSolarSystem_txtGrow, Str(WorkSolarSystem\GRow)) SetGadgetText(#Gadget_frmSolarSystem_txtGCol, Str(WorkSolarSystem\GCol)) SetActiveGadget(#Gadget_frmSolarSystem_txtName) Repeat EventID =WaitWindowEvent() MenuID =EventMenu() GadgetID =EventG...
Read more

Connecting the Forms to the Data-Layer (part 8)

 So now we are down to just the SolarSystem Code Sheet. This is NOT a rubberstamp of the Galaxy. The MAIN reason is that the Galaxy Records are Sourced directly from the Database, As you will recall our SolarSystem is Sourced from the Galaxy Record's Solar System Collection NOT the Database. This makes for a VERY Significant difference between in the code. Our Procedure are the save ALL the Steps are the same, the differences are in the details. Starting once again at the top, we have our declares: Define quitfrmSolarSystem Declare SolarSystemCustom() Declare SolarSystemSetScreen() Declare SolarSystemCreate() Declare SolarSystemModify() Declare SolarSystemDelete() Declare SolarSystemSetData() Declare SolarSystemSave() Declare SolarSystemClose() And then, as before the SetScreen Procedure, and Control-Loop. Procedure SolarSystemSetScreen() Protected String$, x, y, w, h, i, ID Shared WorkSolarSystem Protected EventID, MenuID, GadgetID, WindowID, Index Shared quitfrm...
Read more