Codeunit 5080 "Image Handler Management"
Base Application · System.Media
Across versions
- BC23present
- BC242 procedures changed
- BC25-30unchanged
Neighbourhood 2 connected objects and pages
Base Application · System.Media · BC23-30 · source at ea08af5e · facts from BC29
Procedures
ScaleDown(var SourceImageInStream: InStream; var ResizedImageOutStream: OutStream; NewWidth: Integer; NewHeight: Integer)ScaleDownFromBlob(var TempBlob: Codeunit "Temp Blob"; NewWidth: Integer; NewHeight: Integer): BooleanΔ BC24SetQuality(NewImageQuality: Integer)GetImageSize(ImageInStream: InStream; var Width: Integer; var Height: Integer)GetImageSizeBlob(var TempBlob: Codeunit "Temp Blob"; var Width: Integer; var Height: Integer)Δ BC24
Plus 1 local procedures.
Calls
From the extracted call graph of BC29 (graphify-al on the snapshot checkout): calls whose target is known from a declared type or an Object::"Name" argument. Interface dispatch and calls through events are not counted, so the list is not complete.
- Codeunit 4100 “Temp Blob” (5 calls:
GetImageSizeBlob → CreateInStream,GetImageSizeBlob → HasValue,ScaleDownFromBlob → CreateInStream, …)
Called by
- Codeunit 2114 “O365 HTML Templ. Mgt.” (3 calls:
FillCompanyLogo → ScaleDownFromBlob,ResizePaymentServiceLogoIfNeeded → GetImageSizeBlob,ResizePaymentServiceLogoIfNeeded → ScaleDownFromBlob)
Ask your agent
Procedure bodies are not stored here (D10). The call sections above are our own, per object, from the BC29 call graph. For a procedure body or the calls of one procedure, ask bc-code-atlas (external, by Stefan Maron, MIT; default corpus w1-28), which the bc-observatory plugin connects: bcatlas_resolve_node(object_type: "codeunit", object_name: "Image Handler Management"), then bcatlas_get_procedure_body or bcatlas_get_neighbors on the returned id.