After processing the DEBUG command, the debugger opens several windows, to review execution status.

One of these windows allows inspection of local and global variables.

Double clicking on any variable opens a window labeled VARIABLE_NAME:" Inspect/Modify".

Questions:

1) How can I call this window directly from within a program, without invoking the debugger? What are the required parameters?

2) Is it possible to open this routine instead of the normal system editor with this window? (This gives much better control when editing records with @vm, @svm etc.)

Best regards

Wilhelm

The debugger is a separate C++ program and as such cannot easily have child windows accessed directly from Basic+.

The Sprezzatura Group

World Leaders in all things RevSoft

Wilhelm,

Double clicking on any variable opens a window labeled VARIABLE_NAME:" Inspect/Modify". … (This window gives much better control when editing records with @vm, @svm etc.)

It does?

How do you delete a delimiter from that window?

- Oystein -

Oystein ..

Surely, you jest (pun-intended). It is a supreme PITA to delete delimiters. You CAN inspect / change values by double-clicking to get the data to expand levels (all the way down to the sub-value/text-value level).

Don M.

Oystein,

It does? YES

What is your recipe to cope with frustration, when editing a record with extensive use of SVM, TM, STM?

Even on the VM level, the system editor is everything else than developer-friendly in this respect.

Most of the time I prefer to edit complicated records in AREV. Therefor I am looking for a way to use something similar to the Inspect/Modify window to include in any program for record editing.

According to Sprezzatura, this routine cannot be called directly from within Basic+

Regards

Wilhelm

This is klutzy as the proverbial but

Subroutine EditRow( Table, RowId)

    Open Table To vTable Then         Read Row From vTable, RowId Then             SaveRow=Row             Debug             If Row # SaveRow Then                 Write Row On vTable, RowId Else Call FsMsg()             End         End     End

Return

and then when in the debugger use the drill down to make the changes you want and then just continue.

[size=2]To use just RUN EDITROW "Table","Row" in the

system editor.

The Sprezzatura Group

World Leaders in all things RevSoft

Thanks for the option Sprezz,

but in this case I rather prefer AREV for record editing.

Regards

Wilhelm

Don,

what is a PITA? Sounds exotic…

Wilhelm

Wilhelm,

What is your recipe to cope with frustration, when editing a record in System Editor with extensive use of SVM, TM, STM? Even on the VM level, the system editor is everything else than developer-friendly in this respect.

I agree the hierarchical view of the Inspect/Modify window is nice. But it would be much better if you could get at the delimiters and not just the values between the delimiters. At least in System Editor all the delimiters from @VM downwards are visible characters, and therefore editable. Likewise is @FM, which shows as line break, editable. Also all those characters are available from the keyboard (at least a Norwegian keyboard), even if it's not obvious that e.g

is a @TM.

While I'm at it - I have another reason to dislike the Inspect/Modify window. While debugging you might open that window to follow the development of a variable's content. You drill down through subvalues and subsubvalues etc to expand the detail of your focus. But once you step further through your program execution the whole value collapses and the content scrolls back to the top. Bummer! Revelation - if you read this, please consider if this behaviour can be changed.

Also consider if it would be possible to modify the Inspect/Modify window so editing of delimiters become possible.

But back from my debugging woes to your problem - it shouldn't be too difficult to make a window where one can show the hierarchical structure of a value, like the Inspect/Modify window does, and make the sub(sub(sub))values editable. Neither should it be too difficult to include functionality for inserting and deleting delimiters, in a user-friendly way. How difficult it is to satisfy the rest of your needs depends on exactly what it is you need. What is your scenario? Do you have a window where you can load and save records? And e.g one edit line per field? And then the value in a field (edit line) might have an inner structure with delimiters (i.e, the field is multivalued, possibly with sub etc values)? And then you want to be able to pop up an Inspect/Modify window to get at the detail? That shouldn't be difficult.

Wait a minute. Sprezzatura - how's your old plan for a new Table Browser coming along? Even if you've ditched the plan you must have had some ideas on how to inspect and modify multivalues etc.

- Oystein -

Don,

It is a supreme PITA to delete delimiters.

"Supreme PITA" seems to indicate it can be done. But it can't, can it? Not in the Inspect/Modify window?

- Oystein -

Don,

It is a supreme PITA to delete delimiters.

"Supreme PITA" seems to indicate it can be done. But it can't, can it? Not in the Inspect/Modify window?

- Oystein -

Don,

Sorry for posting twice, but I got so excited because I suddenly discovered it can be done! Just flip the frigging window! The delimiters are on the backside!

- Oystein -

Wilhelm,

That latest posting - that's how I cope with frustration.

- Oystein -

Wilhelm

Schmerz im Arsch.

- Oystein -

Sprezz,

May I suggest a klutzy improvement? (Improvement both as in adding features and raising the klutz level.)

Set aside one character you don't need for anything else. Use this character as a backspace or delete character when you edit Row in the Debugger's Inspect/Modify window. The character won't actually delete anything while you work in the Inspect/Modify window. You must do the deletions programmatically after the debug statement.

Set aside another character you don't need for anything else, e.g, #. Use this character as an escape character for two-byte sequences meaning @VM (e.g #3), @SVM (e.g #4), etc. Now you can also insert delimiters in the Inspect/Modify window. Again you need post-processing after the debug statement, to get the real delimiter values in.

If this isn't enough then do it blindfolded.

- Oystein -

I have a method that I use thats around about 5/10 on the klutz scale.

I created a simple debug program for viewing and modifying variables. In your program you call this custom debug program, pass the variable you want to inspect/modify.

eg: call TEBUG(somearray)

The TEBUG program has a number of view options, such as straight dump, HEX dump, delimiter formatted array such as what the OI debugger shows. These view options also have a search option. There is an edit option that uses an edit window (from the OI TCL program I wrote years ago). This edit program has the exact same functionality as Arev when it comes to editing multi-valued lines. Each time you press ctrl-E on a line it goes to the next level of sub-values.

The logic of this isn't too difficult. If anyone is interested, I can go into more detail.

Paul,

"If anyone is interested, I can go into more detail."

Count on me

Regards

Wilhelm

Create a window with an editbox to edit your data/variable contents with. On the char event, check for ctrl-E. Get the current line of text that the cursor is on. eg text. Use a common variable to keep track of the sub-value level you are on. Increment this by one.

The multivalued char will be 254-level@. Swap char(254-level@) with char(13):char(10) Call the sub-value window to display and edit the contents. eg set_property (windowname: "*" :level@:".EB_MV_EDIT","TEXT",newdata) If ctrl-E is pressed again, repeat the process of recursion. I use a main window and one sub-value editing window and call the sub-value window repeatedly for each level of recursion. Just add *Levelno to the end of the windowname so you can call a new instance each time. You may be able get away with just one window to do the lot, mine was created as an afterthought. When saving changes from multiple levels deep, just do the opposite to step backwards. Convert char(13):char(10) to char(254-level@) then set_property(windowname:"*":level@-1:".EB_MV_EDIT","TEXT",newdata) then close the current window etc.

PITA - Pain In The A*s.

Don M.

Oystein ..

Well .. not easily but …

You CAN get at the data so .. you can copy it with CTRL+C and then .. in another editor which you happen to have open .. CTRL+V (paste). You CAN edit it there and then reverse the process. The trick is to be running OI in it's own workspace so that you can task switch to another program. Ugly, but it works. I use METAPAD as an editor which allows the ALT+numericpad stuff to be put in.

Not a pretty sight .. but ..

Don M.

View this thread on the forum...