martinako's profile - activity

I know what's going on. If I select a large section of commented text and run this script, it sends it to the debug cons

It's in ubuntu 22.04. Yes, the console is back in the prompt. When I press up arrow, sometimes I get something else I ha

correct paste error

Work around needed. How to repeat last command in the debug console, despite there was an 'undo' ? I have a custom scrip

Work around needed. How to repeat last command in the debug console, despite there was an 'undo' ? I have a custom scrip

Hi, I have a script that I've used in the past with older versions of WingIDE. It evaluates in the debug probe the commented selection. I don't really remember where I got the script from but it doesn't work in WingIDE ver 10.

I wonder if someone who knows about scripts for wingIDE can tell me how to update it so it can work in wingide 10. This is the script:

from __future__ import with_statement

import os.path, sys
sys.path += [
    os.path.dirname(__file__), 
    os.path.join(os.path.dirname(__file__), 'third_party.zip'), 
]

import wingapi

def comment_evaluate_sel_in_debug_probe(editor=wingapi.kArgEditor):
    '''
    Evaluate a commented selection in debug probe, do `select-more` if no selection.
    Suggested key combination: `Ctrl-Alt-D`
    '''

    assert isinstance(editor, wingapi.CAPIEditor)
    wingapi.gApplication.ExecuteCommand('comment-toggle')    
    wingapi.gApplication.ExecuteCommand('evaluate-sel-in-debug-probe')
    editor.ExecuteCommand('undo')

When the script load an error message appears with:

Runtime failure details:
Exception: "<class 'AttributeError'>"
Value = "module 'wingapi' has no attribute 'kArgEditor'"

That works! thank you very much!

Probably old wingapi Hi, I have a script that I've used in the past with older versions of WingIDE. It evaluates in the

I evaluate a section of code in the debug probe and it executes in the current context as expected. However, when I press up cursor to repeat the last executed block of code in the history it's not there anymore! so I have to make a selection of the code and evaluate again. Which breaks my focus as I have to repeat that same selection may times in a debug task.

For a test, I do the same for a smaller section of the same code. When I press the up cursor it's there. I start to increase the size of the code block and when it reaches 24 lines it stops remaining in the history.

Is there a setting anywhere that controls the maximum size of the executed code that goes in to the history? or is this a limitation? I started a new project in case the project files where corrupted but it didn't make any difference.

I'm using winpro 7.2.9.0

Debug probe last evaluated code selection doesn't remain in history I evaluate a section of code in the debug probe and

Debug probe last evaluated code selection doesn't remain in history I evaluate a section of code in the debug probe and

I would like to have the same font zoom for all documents. At the moment the document seems to remember the zoom (I set the zoom with Crtl+Mouse wheel) and as I work in two environments with different screen sizes I'm all the time zooming in and out each document depending on the environment I am, this becomes tedious after a while. Is it possible to do something like this?

Same zoom for all documents I would like to have the same font zoom for all documents. At the moment the document seems

I've just tried wingpro7 and I see the icons in the project browser have changed wrt. wingide6. I prefer plainer icons in file browsers as I'm dyslexic and I unconsciously get stuck with fancy icons and specially outline only icons (as they are easier to confuse with the outlines of letters just beside) like the default folders in wingpro7. So it takes me longer just to locate a file. Is it possible to change these icons? the wingide6 ones were fine.

Yes, filled icons distract me less. I guess you could offer a couple of sets of icons to chose from the settings, the ol

I'm debugging various scripts running in a docker container. I can debug them fine following the instructions in here https://wingware.com/doc/howtos/docker However, the "Move Program Counter Here" command, which I often use, is greyed when I debug scripts running in a docker container. The command it's available when debugging a script in the host. I've tried to call the command directly from the "Command by name" option and typing debug-move-counter or debug-move-counter-clicked, which works well when debugging a script in the host, but I get the message Command not found.

I've run the "Reload all scripts" option but it the debug-move-counter is still not available.

How can I make this command available when debugging a script inside a docker container?

Change project browser icons in wingpro7 I've just tried wingpro7 and I see the icons in the project browser have change

I've done the same steps with wingide7 and I can use the debug-move-counter command there without problem. So the proble

I'm using wingide6. There is no exception and it's innermost stack frame. I use that command often. I have just tried to

I'm using wingide6. There is no exception and it's innermost stack frame. I use that command often. I have just tried to

"Move Program Counter Here" command not available when debugging script in a docker container I'm debugging various scri

I've managed to attach the wingide debugger to the script running in the container. However, I'm not sure of the necessa

Unable to connect debugger to a docker container I'm following the example in here to connect the WingIDE debugger to a

Unable to connect debugger to a docker container I'm following the example in here to connect the WingIDE debugger to a

When I use host.docker.internal:50005 it just fails to connect, it doesn't time out. I'll update the question with the l

I had already tried kWingHostPort = 'host.docker.internal:50005' before posting. I've tried again and the logging is fin

Unable to connect debugger to a docker container I'm following the example in here to connect the WingIDE debugger to a

I had already tried kWingHostPort = 'host.docker.internal:50005' before posting. I've tried again and the logging is fin