Set mouseStart to mouse cursor x/y coordinates onMouseDown about atom-sublime-select

[bigfive]

Yeah its a shame about the lack of bufferPositionForPixelPosition(position)

At the moment I have to hijack the standard selection method in order to get rows and columns. That means I have to allow atom to do a normal selection and then override the selected ranges, which causes that horrible flickering and random selections appearing. Not ideal but the best I can do ATM

I'm not sure I know what you mean about the clicking and reseting cursors?

[iccir]

I'm not @Egidius, but this is what I'm seeing:

Let's say I have this text in my editor:

 foo bar baz
 foo bar baz
|alpha beta gamma delta
 moo oink bah

With the cursor in front of alpha. I want to column select foo of the first two lines. I alt-click the top-left of the first foo, then drag to the bottom-right of the second foo.

I expect both foos to be selected, what I end up with is...

[iccir]

In Sublime, I end up with two cursors, at the end of both foo's, and both foos are properly selected.

[iccir]

onMouseDown uses editor.getCursor().getBufferPosition() and assigns that to mouseStart, but in the above example, getBufferPosition() correlates to the beginning of alpha, not the beginning of foo (where I clicked). So you end up with mouseStart being the buffer coordinates of alpha and mouseStartPx being the pixel coordinates of foo

[bigfive]

Ah I see.
Ive recently updated to v1.0.2. Its a complete rewrite of the selection generation.
Ive written a 'screenPositionFromMouseEvent'. Let me know if that fixes the issues

[iccir]

Nice! It seems to be working a lot better now! Thanks :)