> >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.
Tk will handle continous Shift-click's. I thought this was a cool
feature, and I found it super easy to add. I'll be committing it shortly.
> >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.
I added this as an option in the "Colors" preference tab and added
the code to take it into account. Will commit shortly. 0-]
> >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.
This is right up Christian's alley. 0-]
>
> >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.
I'm not sure what the hell you people are talking about. 0-]
> >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.
I'll make it remember. This will be committed shortly.
> >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.
I actually took this out of a program I wrote recently. I will commit
shortly. 0-]
D
_______________________________________________
vtcl-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/vtcl-user
