Actually, I know how to change the parameter:
picc configure -data {
#define picc_width 2
#define picc_height 2
static char picc_bits[] = { 0xff 0xff }:
}
will do the job. However, I want to display a video sequence in TCL and the best way I can thingk of doing it is by writing each frame as a bitmap on a canvas. The source of the video information isn't important (let's assume it's a file) and the format is the same as a b&w (well grayscale) bitmap image.
A bitmap image (vid_frm) would be displayed on the canvas and then each new frame of data would be read into a variable 'next_frame' and then used to update the data for vid_frm:
vid_frm configure -data {
#define vid_frm_width 128
#define vid_frm 256
static char picc_bits[] = $nextframe
}
Unfortunately, this does not treat $nextframe as a variable and instead tries to set the bitmap data to the string "$nextframe".
So, how do I persuade TCL to treat $nextframe as a variable?
TIA
Joe
picc configure -data {
#define picc_width 2
#define picc_height 2
static char picc_bits[] = { 0xff 0xff }:
}
will do the job. However, I want to display a video sequence in TCL and the best way I can thingk of doing it is by writing each frame as a bitmap on a canvas. The source of the video information isn't important (let's assume it's a file) and the format is the same as a b&w (well grayscale) bitmap image.
A bitmap image (vid_frm) would be displayed on the canvas and then each new frame of data would be read into a variable 'next_frame' and then used to update the data for vid_frm:
vid_frm configure -data {
#define vid_frm_width 128
#define vid_frm 256
static char picc_bits[] = $nextframe
}
Unfortunately, this does not treat $nextframe as a variable and instead tries to set the bitmap data to the string "$nextframe".
So, how do I persuade TCL to treat $nextframe as a variable?
TIA
Joe