>1. I would like to program around widget events. I go into OPTIONS and >then BINDINGS. There I think I see the current code for each event. >How do I write code for an event (such as double clicking on a list box)
In the left pane of the bindings editor, click on the blue text showing
the widget path (usually the first item in the left pane).
Then in the menu bar of the bindings editor, select Insert
and choose the type of event. If not in the list, use "Advanced..."
To add a modifier (eg. double, triple, shift...) to an event, right-click
on it.
>2. Stack trace window is confusing. I can change the code in that
>window, but it doesn't take effect. Could an alternative be to have a
>button to call up the code in question.
You cannot change code in the stack trace window. Yes, there could be a
button to open the proc editor.
>3. Closing of code windows should save by default. I don't think I
>should have to close using the check to get my stuff to save. Since
>most people want to save changes, shouldn't the default be that.
This would make sense. All other places like the menu editor and the
bindings editor don't ask you to save.
>4. When I switch over to "TEST" mode, all code open should save.
Would make sense too.
>5. The editor is really bad at guessing what to do when I press ENTER.
>If I am at a }, it replicates that down a line.
That's a bug. Still the original code to auto-indent, it doesn't work very
well.
Could you enter 2,3,4 as feature requests and 5 as a bug ?
Thanks!
CG
|--------+------------------------------------->
| | Robert Lugg |
| | <[EMAIL PROTECTED]|
| | > |
| | Sent by: |
| | [EMAIL PROTECTED]|
| | eforge.net |
| | |
| | |
| | 12/11/2001 02:49 PM |
| | |
|--------+------------------------------------->
>-----------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Fax to:
|
| Subject: [vtcl-user] Problems/improvements with vTcl 1.5.2
|
|
|
>-----------------------------------------------------------------------------------------------------------|
I have notices a couple of things while using vTcl. Would someone(s)
look at these and tell me if they are bugs or just something I'm doing.
1. I would like to program around widget events. I go into OPTIONS and
then BINDINGS. There I think I see the current code for each event.
How do I write code for an event (such as double clicking on a list box)
2. Stack trace window is confusing. I can change the code in that
window, but it doesn't take effect. Could an alternative be to have a
button to call up the code in question.
3. Closing of code windows should save by default. I don't think I
should have to close using the check to get my stuff to save. Since
most people want to save changes, shouldn't the default be that.
4. When I switch over to "TEST" mode, all code open should save.
5. The editor is really bad at guessing what to do when I press ENTER.
If I am at a }, it replicates that down a line.
If these are things that should be in bugs in SourceForce, I'll enter
them.
Thanks,
Robert
(See attached file: robert_lugg.vcf)
robert_lugg.vcf
Description: Binary data
