Quote from
HPW on August 9, 2021, 10:52 pm
Hello,
A few sample out of the dev-version:
SetObjectFileName "Picture1" "[MimeStream]J4040.png"
ImageWindow "Show MimeContent" "-1" "-1" "[MimeStream]J4040.png"
PopUpImage "-1" "-1" "[MimeStream]J4040.png" "0" "None" "0"
Every command which currently supports [Embedded] graphics should work now with [MimeStream].
In the past there was a sampe for hpwKnobCreate (hpwUtility). The last demo shows how 15 images are dynamicly created in hpwImage and used for the Knob.
And last but not least the new Zip commands will support InMemory-Zips. As also embedded zips.
So embedding gets a subfilesystem which supports pathes.
Many other uses might be possible.
Regards
Hans-Peter
Hello,
A few sample out of the dev-version:
SetObjectFileName "Picture1" "[MimeStream]J4040.png"
ImageWindow "Show MimeContent" "-1" "-1" "[MimeStream]J4040.png"
PopUpImage "-1" "-1" "[MimeStream]J4040.png" "0" "None" "0"
Every command which currently supports [Embedded] graphics should work now with [MimeStream].
In the past there was a sampe for hpwKnobCreate (hpwUtility). The last demo shows how 15 images are dynamicly created in hpwImage and used for the Knob.
And last but not least the new Zip commands will support InMemory-Zips. As also embedded zips.
So embedding gets a subfilesystem which supports pathes.
Many other uses might be possible.
Regards
Hans-Peter
luishp, Vadim and rcohen have reacted to this post.