Hi, here are a few more problems/suggestions, that I have after using 1.5.2 for a while. Great tool!
Using 1.5.2, I did this: --------------------------------- progressbar after save problem Create new project, add a frame, add a progress bar to that frame. It will be alias Progressbar1. If you add one more now, it becomes Progressbar2. Ok. But, say instead, you write out the project, quit, startup and load the project back in. Then if you add a progressbar it too becomes progressbar1. Then you try to save and you get: can't read "widget(Progressbar1)": no such element in array and the save fails with only 1/2 the file written out. --------------------------- progressbar color Changing the color of the progressbar and then saving, it reverts back to @blue0 --------------------------- progressbar variable What does the progressbar variable do. Does it work? ---------------------------- place/pack/grid manager It would be nice if there were a way to change the manager for a set of widgets in a frame. Say, from all pack to all grid or back. --------------------------- Keyboard shortcuts Here are some I would like to have. When the widget tree is active: down/up-arrow make next/prev widget in tree active. Great for a row of buttons to go through a bunch. letters for attributes: Would rotate the choices, w/o making the attribute menu active, but would show in its widgets. a nchor e xpand f ill s ide This way I could quickly w/o mousing at all, change a row of buttons. One could get a nice rhythm going, down, e, down, e to change all to expand from the default of not to, or down f,f,f down f,f,f to change all from none to both fill. ---------------------------------- user compounds from samples do these work (not for me) ------------- bug create a new top project create a frame in it create a scrolling canvas (compound) try to add a frame to the frame holding the scrollable canvas program freezes. --------------- suggestion menu with default pack settings (left/right etc.) or use settings from current selection ----------------- question I'm not exactly sure why main is invoked when loading vtcl. I get into trouble sometimes. I had some code that created it's own graphics. I accidentally called the setup routine from main, without protecting it from being called during a vtcl session. After the save, the next load was all messed up since it had remembered all the widgets I'd created. I had to go back a few versions to get one that worked. Perhaps you should have 2 mains, one that gets invoked during vtcl and one only at runtime of the project. I guess the reason is so that test mode can work. But I never use test mode. Maybe a pref setting to "not invoke main when editing". _______________________________________________ vtcl-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/vtcl-user
