I’ve found how to bind my own command to ctrl+click, but now I’m struggling with obtaining current position of the cursor. Doing view.sel()[0] is obviously unreliable, so I’m looking for a better way.

A great solution would be to get mouse coordinates of the click, convert them to text coordinates via view.layout_to_text and do my stuff. After enabling sublime.log_commands I’ve noticed that Sublime passes mouse coordinates to drag_select handlers (e.g. “command: drag_select {“event”: {“button”: 1, “x”: 582.5, “y”: 274.5}}”). However, I’ve been unable to get hold of them - neither bound by press_command, nor by command in sublime-mousemap entry, my command doesn’t receive the “event” argument.

Any ideas?

Let me know if you figure out how to do this—I tried briefly a while ago but I don’t think I found anything.

Normally it’s simply part of the args variable:

[code]import sublime, sublime_plugin

class TestPluginCommand(sublime_plugin.TextCommand):
def run_(self, args):
print args’event’]
[/code]

I tried to play with this but i had issues converting reliably (x,y) to test position (it was some times ago but maybe things are better now …). So in the end what i did was pass the arg to the drag_select command, and then use view.sel()[0].
This was for a plugin to emulate a kind of drag&drop (more a sel&click) before it was implemented: you can find the very simple source here: bitbucket.org/Clams/pasteselonclick/src

Didn’t work for me. The second argument is just a plain Edit object, which cannot be indexed. Could you, please, post your mousemap?

{ "button": "button2", "modifiers": "alt"], "press_command": "paste_sel_on_click", "press_args" : {"del" : true} }, { "button": "button2", "modifiers": "alt","ctrl"], "press_command": "paste_sel_on_click", "press_args" : {"del" : false} } ]

Ah I see! run_ (with an underscore) strips the event from the arguments list before calling run (no underscore). So you have to override run_ instead of overriding run.
Awesome.

I don’t think wbond’s package manager does anything with dependencies, but I just wrote a cool mouse-callback thing:
gist.github.com/2979613
It lets you inherit from MouseEventListener and then you get an on_pre_click with the args and an on_post_click with the position in the file where the user clicked.
I think I might upload it to github and make it a real repo, and then I’ll make my ScrollOffset plugin ignore mouse input. Now that would rock!

[quote=“adzenith”]Ah I see! run_ (with an underscore) strips the event from the arguments list before calling run (no underscore). So you have to override run_ instead of overriding run.
Awesome.[/quote]

Woot! What’s the difference between run and run_?

/quick thread hijack:

@adzenith I was checking out your ScrollOffset plugin earlier today. I use a similar plugin that always keeps the cursor centered, so I thought your “mouse-callback thing” may be solving similar problems as the ones I am encountering. Honestly, I can’t figure out what it’s supposed to do. What I was looking for is disabling the click+hold for selection so that I could only use mouse button 1 to change the cursor’s location. (I would then use shift+click for selection). With the aforementioned plugin, my thumb has a bad habit of tapping the touchpad, selecting chunks of text which I then gleefully proceed to overwrite without noticing… Hope this makes, sense

The mouse-callback thing is not yet integrated into my ScrollOff plugin, which may have explained what you were seeing.
My plan was to capture on_pre_click, disable ScrollOff for the next on_selection_modified, then capture on_post_click and re-enable. This would make it so that clicking wouldn’t scroll the display, allowing normal selections with the mouse. Does that make sense?

[quote=“xeno.by”]

[quote=“adzenith”]Ah I see! run_ (with an underscore) strips the event from the arguments list before calling run (no underscore). So you have to override run_ instead of overriding run.
Awesome.[/quote]

Woot! What’s the difference between run and run_?[/quote]

That’s the entire difference right there. run doesn’t get the event.

I wasn’t clear, sorry. I tried the Scroll Off plugin and the mouse stuff separately (one after the other). If the latter only works with the former, then that’s why I didn’t see any effect. Or maybe I still don’t understand what it’s supposed to do.

Sort of. (I’m not a programmer and your explanation is a little technical.) I’ll keep an eye out for what you’re building and see if it might work for me also, although probably not out of the box.

In the meantime I would be quite happy with just disabling the mouse (or, at least, button 1) altogether when my plugin is enabled, but “context” seems to be ignored in mousemaps. Darn.

I just pushed my changes. Try installing both ScrollOffset and MouseEventListener and tell me if you like what you see.

You should put something in the README about the fact that ScrollOffset only works when word wrap is off

ScrollOffset looks like a plugin I might well use (for coding, which is a different situation than the one I’ve been talking about).

As for using MouseEventListener with my typewriter plugin, I didn’t manage to get anything particularly useful done.

I’ve thrown up the plugin below, if you don’t mind having a look. (But I don’t mean to impose.)

import sublime, sublime_plugin

class AlwaysCenterCommand(sublime_plugin.EventListener):
	def on_selection_modified(self, view):
		if view.settings().get('typewriter_mode') == 1:
			sel = view.sel()
			region = sel[0] if len(sel) == 1 else None
			if region != None:
				view.show_at_center(region)

The plugin keeps the cursor always centered. What I’ve been hoping to do is to prevent is extending the selection with mouse clicking. Is this possible?

Again, feel free to ignore this stuff.

I guess I never use word wrap… Maybe I should look into why it doesn’t work.

I’d install MouseEventListener, then in your AlwaysCenterCommand add this:

ignore_count = 0 def on_pre_mouse_down(self, args): self.ignore_count = 3 def on_post_mouse_down(self, click_point): self.ignore_count = 1

Then inside of on_selection_modified, throw this at the top:

if self.ignore_count: self.ignore_count -= 1 return

Lemme know if that works.

typewriter_mode was added to bufferscroll, did you have some problem with this plugin? I want to fix it, if that is the case.

REgars,

Hi @tito,

I am not using your BufferScroll plugin, so there isn’t anything related to that for you to fix. If you’re offering your excellent services though…

I am using the plugin I posted above; it’s slightly modified from something @facelessuser has written1. This plugin activates on “on_selection_modified” rather than “on_modified” (as is the case with BufferScroll). This means that the screen is scrolled every time the cursor changes position,which works great when you are:

a) writing prose rather than code,
b) using the keyboard rather than the mouse

Unfortunately, the functionality of the mouse is quite broken: it’s too easy to select text when trying to position the cursor. I haven’t actually used iA Writer2, but it disables the mouse completely, I suspect for this reason.

I actually rather like how it works, if only I could disable extending the selection on mouse click.

I understand, I’ll take a look after lunch, I’m interested into providing better behaviour for these features.