Stats

  • Replies 8
  • Subscribers 159
  • Views 2712
  • Members are here 0
More Content

axlFormTreeViewLoadBitmaps() - Doesn't seem to work

mikebystedt

I've got a form with a tree view field.  I'd like to change the bitmap image for the leaf nodes.
However, no matter what I try, I can't seem to get them to load.  I know my form is there, the
field is "tree", and my bitmap file is "EU.bmp".

I know the 16X16 bitmap is there because isFile("./EU.bmp") tells me so.  Ultimately I want to be able to
load it from a central location on a server, but can't even get that far.

The following attempts all resulted with a return of "nil".

bmpHandles = axlFormTreeViewLoadBitmaps( checkForm "tree" list("A:/SkillBeta/Skillcheck/Images/EU"))
bmpHandles = axlFormTreeViewLoadBitmaps( checkForm "tree" "EU")
axlFormTreeViewLoadBitmaps(checkForm "tree" list("EU"))
axlFormTreeViewLoadBitmaps(checkForm "tree" list("./EU"))
axlFormTreeViewLoadBitmaps(checkForm "tree" list("./EU.bmp"))
axlFormTreeViewLoadBitmaps(checkForm "tree" "EU.bmp")
axlFormTreeViewLoadBitmaps(checkForm "tree" "EU")
etc...

Any suggestions?  Has anyone gotten this to work?  There is no example in demo axlform.il file,
and the documention is even partly incorrect in it's example:

Example
Given the file myBmp1.bmp is a 16 x 16 bitmap and myBmp2.bmp is a 32 x 16 bitmap.
(axlFormTreeViewLoadBitmaps (list "myBmp1" "myBmp2"))
This might return the following:
(6 7 8)

Thanks in advance,

-Mike

  • Anybody out there ever used this?  

    Thanks,

    -Mike

  • Try the following:

    Loading the bitmaps (assumes BMPPATH has "." in it and your files have a .bmp extension and your TREE control has a label "tree")

          - also bmps are 16x16. If wider then become multiple bitmaps. For example if your bitmap is 16x32 then the 1st 16 pixels is mapped as the 1st bitmap and the last 16 pixels becomes the 2nd bitmap

        l = axlFormTreeViewLoadBitmaps(fw "tree" list("myBmp1" "myBmp2" "myBmp3"))


    You have added a tree item by:

          treeItem = axlFormTreeViewAddItem(fw "tree" "one" nil nil 'TVSELECT_3STATE)

    You can change the bitmap(s) by

          axlFormTreeViewChangeImages(fw "tree" treeItem car(l) cadr(l) nil)

       

       

      

  • Ahhh. I think my issue was the BMPPATH! I'll give it another shot. Thanks! -Mike

  • I'm seeing some very strange results for the handles.  Any clue what may be going on here?
    My env file contains:  set BMPPATH = "."  (Not positive that this is the correct syntax).

    NEED HELP Please!   Thanks, Mike.

    l = axlFormTreeViewLoadBitmaps(checkForm "tree" list("EU"))
    (54305580 1964135525 -1862200948 109119504 4
    0 -1 109119440 0 54305576
    54305620 0 0 0 54305720
    1 36 1 25165833 54305832
    1964134770 -1862200948 255848152 4 54305632
    1988913760 1989197852 1 1988852463 23
    -1862200948 1024 54305832 1964134834 54305720
    37 13 1964135041 0 54305636
    9502821 54305832 255848152 458339612 -2
    1965543519 1965515514 2754996 20 1
    0 2000628727 -591746099 0 0
    2000628727 23 0 1965949488 40
    54305848 1965518225 1965518161 1833615692 20
    2000628727 55269344 36 1 55711760
    55731484 112 -55711761 -55731485 1965518057
    1965518225 20 1 0 0
    54305756 1833596263 54305884 1964119056 -1862200948
    13 0 1 40 0
    255848152 4 1 37 0
    54305948 1965562008 -1862200948 13 0
    255848152 4 1 37 1
    5 1717225984 55878632 1717226012 1717225984
    54306000 1716453537 1717226012 -988800001 55593016
    55269344 1716454307 1833615814 -988800001 54306804
    55269344 2000544652 -172831042 54306980 3
    58629664 54306312 39398300
    )

  • Do a RMB and select Properties on your bitmap file, eu.bmp


    Go to Details tab and look at the width and height values. The height should be 16 pixels and the width should be a multiple of 16.

    If not edit the bitmap and fix it so it meets these rules.

Cadence Guidelines

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.