Skip to main content

[archive] W$Bitmap Problem

  • June 18, 2008
  • 4 replies
  • 0 views
D

[Migrated content. Thread originally posted on 17 June 2008]

I am having a problem with a bitmap.

I am doing call "W$BITMAP" using WBITMAP-DISPLAY, file-name, 4, 1
giving ws-bitmap-handle.

What I have is a bitmap that is created by a user and a different user diplay's it on there screen. This works ok the first time.

Bitmap file name is root-mhb.

After the first time the bitmap is displayed and the program that display's the bitmap is closed the 1st user creates another bitmap with the same name.

When the second user tries to display the bitmap it displays the first bitmap not the current one in the file.

I have added call "W$BITMAP" using WBITMAP-DESTROY, ws-bitmap-handle

Which is executed before the user exits the program, but every time after the first time it still displays the first bitmap. It has to be pulling it from memory because the bitmap image in the file is different from what is displaying. I am using thin client on a Linux system. The only way after the first time, I can get it to display the correct image is by loging off of my Windows work station.

Can someone let me know what I am doing wrong. ACUGT and ACUConnect 7.1

Thanks

    4 replies

    D

    [Migrated content. Thread originally posted on 17 June 2008]

    I am having a problem with a bitmap.

    I am doing call "W$BITMAP" using WBITMAP-DISPLAY, file-name, 4, 1
    giving ws-bitmap-handle.

    What I have is a bitmap that is created by a user and a different user diplay's it on there screen. This works ok the first time.

    Bitmap file name is root-mhb.

    After the first time the bitmap is displayed and the program that display's the bitmap is closed the 1st user creates another bitmap with the same name.

    When the second user tries to display the bitmap it displays the first bitmap not the current one in the file.

    I have added call "W$BITMAP" using WBITMAP-DESTROY, ws-bitmap-handle

    Which is executed before the user exits the program, but every time after the first time it still displays the first bitmap. It has to be pulling it from memory because the bitmap image in the file is different from what is displaying. I am using thin client on a Linux system. The only way after the first time, I can get it to display the correct image is by loging off of my Windows work station.

    Can someone let me know what I am doing wrong. ACUGT and ACUConnect 7.1

    Thanks
    Does your COBOL program use copy resource to bring in the bitmap?

    If so, consider that the bitmap accompanies the object file. You would need to copy the resource again once the new bitmap is made.
    D

    [Migrated content. Thread originally posted on 17 June 2008]

    I am having a problem with a bitmap.

    I am doing call "W$BITMAP" using WBITMAP-DISPLAY, file-name, 4, 1
    giving ws-bitmap-handle.

    What I have is a bitmap that is created by a user and a different user diplay's it on there screen. This works ok the first time.

    Bitmap file name is root-mhb.

    After the first time the bitmap is displayed and the program that display's the bitmap is closed the 1st user creates another bitmap with the same name.

    When the second user tries to display the bitmap it displays the first bitmap not the current one in the file.

    I have added call "W$BITMAP" using WBITMAP-DESTROY, ws-bitmap-handle

    Which is executed before the user exits the program, but every time after the first time it still displays the first bitmap. It has to be pulling it from memory because the bitmap image in the file is different from what is displaying. I am using thin client on a Linux system. The only way after the first time, I can get it to display the correct image is by loging off of my Windows work station.

    Can someone let me know what I am doing wrong. ACUGT and ACUConnect 7.1

    Thanks
    We do not do a copy resource, but we use the following command to load the bitmap:
    CALL "W$BITMAP" USING WBITMAP-LOAD "poss.bmp", GIVING
    poss1-bmp
    Then I can exit the program copy a different bitmap to poss.bmp and when I go back into the program it shows the new bitmap.
    D

    [Migrated content. Thread originally posted on 17 June 2008]

    I am having a problem with a bitmap.

    I am doing call "W$BITMAP" using WBITMAP-DISPLAY, file-name, 4, 1
    giving ws-bitmap-handle.

    What I have is a bitmap that is created by a user and a different user diplay's it on there screen. This works ok the first time.

    Bitmap file name is root-mhb.

    After the first time the bitmap is displayed and the program that display's the bitmap is closed the 1st user creates another bitmap with the same name.

    When the second user tries to display the bitmap it displays the first bitmap not the current one in the file.

    I have added call "W$BITMAP" using WBITMAP-DESTROY, ws-bitmap-handle

    Which is executed before the user exits the program, but every time after the first time it still displays the first bitmap. It has to be pulling it from memory because the bitmap image in the file is different from what is displaying. I am using thin client on a Linux system. The only way after the first time, I can get it to display the correct image is by loging off of my Windows work station.

    Can someone let me know what I am doing wrong. ACUGT and ACUConnect 7.1

    Thanks
    Hello,

    Do you use different bitmap-handle for different photo's?
    If yes, try to use the same bitmap-handle for all of them and see what happens.
    Regards
    Ahmed
    Belgium
    D

    [Migrated content. Thread originally posted on 17 June 2008]

    I am having a problem with a bitmap.

    I am doing call "W$BITMAP" using WBITMAP-DISPLAY, file-name, 4, 1
    giving ws-bitmap-handle.

    What I have is a bitmap that is created by a user and a different user diplay's it on there screen. This works ok the first time.

    Bitmap file name is root-mhb.

    After the first time the bitmap is displayed and the program that display's the bitmap is closed the 1st user creates another bitmap with the same name.

    When the second user tries to display the bitmap it displays the first bitmap not the current one in the file.

    I have added call "W$BITMAP" using WBITMAP-DESTROY, ws-bitmap-handle

    Which is executed before the user exits the program, but every time after the first time it still displays the first bitmap. It has to be pulling it from memory because the bitmap image in the file is different from what is displaying. I am using thin client on a Linux system. The only way after the first time, I can get it to display the correct image is by loging off of my Windows work station.

    Can someone let me know what I am doing wrong. ACUGT and ACUConnect 7.1

    Thanks
    You indicate that you use Thin Client since you mention AcuConnect. Is this happening with both the local runtime and in a thin client execution? If only the latter, this is probably a cache issue. Thin client cache resources like bitmaps. It should notice the change though...
    This might be a candidate for technical support.

    Recent badge winners

    Explore all badges
    Terms & ConditionsAccessibility statement