Thanks for your comments!
>1. The shift/click of the toolbar should let each click add
>some number of similar objects to the same container. After
>a click, the new item is selected. If the last item were still
>selected, then one could add a number of objects, say buttons, to
>a frame with just repeating the shift click, i.e. shift click-click-click
>on a button (with a frame selected) could add three buttons to a frame.
>
>I know there is some case where this worked as I mentioned,
>but I can't seem to repeat it.
I am not sure if Tk can handle Shift then a couple of clicks instead of
shift+click, shift+click, ... maybe handle the Shift down event, then
the clicks, then the Shift up event.
>I tried continuus widget placement, but this got confusing. Every click
>placed something.
Well, that's what it is for :-)
>2. Some missing tree refreshes. e.g. when changing names of buttons.
Yes, it's a bug. When changing button labels the widget tree should
refresh. There are a couple other situations where the tree does not
refresh where it should.
>3. Suggestion, change tree highlight color from blue to red.
>Tryit, you'll love it. Really stands out nicely now.
>
>
>in tree.tcl
>proc vTcl:show_selection {button_path target} {
>...
> $b itemconfigure "TEXT$button_path" -fill #ff0000 <---- (red)
>
This could be an option in the preferences. Try the 1.6 CVS, it has
a couple more color preferences.
>4. Don't seem to be able to set tearoff for the menus in the menubar,
>the options is grey-ed out.
It's a bug. The workaround is to select the "M" widget in the widget
tree and use the attributes editor instead.
>5. need to make shift-insert-compound like shift-click-menu to
>insert into a hidden frame (the active one) easier. I guess you
>could turn off the
Here too, I guess I would have to track the shift key down event first
before the menu item, then track the shift key up event.
>6. The -command windows all open up very small. I had to resize
>them everytime. Maybe these could be remembered somehow?
>Anyway, I changed lib/command.tcl from 350 to 750
>
> wm geometry $base 750x200+[expr $vTcl(mouse,X)-120]+[expr
$vTcl(mouse,Y)-20]
Yes, it would be smarter to remember the size instead of deciding for the
user.
>7. The "are u sure u want to quit" is not necessary. If you change
something
>you already get a warning and can cancel the quit or save or nothing. I
have removed the
>confirmation on quiting. Most other programs work this way. Could be a
settable option.
Good idea.
>Related: simply opening up a command window looks to vtcl as a change.
Even
>if no changes or the cancel are chosen.
That's a bug too.
>8. This is not new, but it bites me once in a while. The split (h/v)
panels are
>very sensitive to adjustment. I find if I ever move the red frame (to
adjust
>the relative start sizes of the panels) I can get a compound that will
>not work properly forever after. My workaround is to never touch these in
vtcl.
I change the size of these panels in TEST mode. They work pretty well for
me.
I have used them in the Visual Text sample application (actually, Visual
Tcl
uses them for the bindings editor, the menu editor and the system
inspector).
>Related: Is there some easy way to make the small red frame larger?
Use the paned window for IWidgets, or set the size in TEST mode.
I could redo the compounds. Windows-like splitters would not be bad too,
instead of the old Motif-like ones we have now.
>9. Minor, maybe a previous button in tip of the day, or reset to
beginning.
Yes. I'll add that to the feature requests.
>10. A few more recent projects, and place them right in the file menu
instead of
>a sub-menu. Just would make it a tiny bit quicker to startup.
I would keep this list very short then (maybe 3 or 4 maximum) to avoid
making
the file menu too big.
>related: On windows, I tried to create a shortcut pointing to a file
>to load (by being the first argv parm on the command line). But something
>would fail after I would write this file out. The program would not
>work properly. I Don't know what happens on unix systems. I do all my
>development on windows.
It's a bug. I fixed it in the 1.6 CVS (main branch).
_______________________________________________
vtcl-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/vtcl-user
