User forums > General (but related to Code::Blocks)

Strange cursor position with wx3.0.2 (scintilla)

(1/7) > >>

headkase:
Edit: Posts in this thread were split from: This thread.

The cursor issues are not new however, I have tried to build with 3.0.2 previously, as in months previously, ever so often and the issue has been present each time.  I always assumed that it was attributable to 3.0.2 not being "baked" enough.  However, I guess I should have reported it a long whiles back.  If the issue is in the Code::Blocks source then it has been present for a good while.

If you have any patches I can test apply to any specified SVN build then feel free to post them.  I will gladly recompile away if it helps to stomp out a bug or few.

Edit: I just rebuilt wxWidgets 3.0.2 64-bit without CFG=64 so I did not have to modify that variable in the SVN 10625 project.  Same error as given above.  I am, as stated in the first post, using MinGW-Builds 5.2.0 64 bit and I also have the 32 bit version as well.

Let's try a different tack.  You tell me exactly which compiler to use and either 32 or 64 bit or both and I will build the wxWidgets 3.0.2 versions with that toolchain.  That way we can also rule out MinGW-Builds as the compiler.

ollydbg:

--- Quote from: headkase on December 18, 2015, 10:48:51 pm ---What happens on my system, I can compile wxWidgets 3.0.2 64 bit with no errors.  Then I can build codeblocks wx 30 64 also with no errors.  Run it, it loads fine.  However, open a text window the cursor caret does not behave properly.  If you go up or down a line it may leave an old cursor bar graphic there, or up or down, left or right, all the arrow keys: it either leaves a artifact or does not update.  Either graphical garbage or an invisible caret.  No errors are thrown at all that I am aware of.  It just doesn't work like it's supposed to.

I am not a technical expert so I do not know where to begin troubleshooting that.  If you provide a concrete list of steps to try and report the results of then I would gladly do them.

--- End quote ---
I have 32 bit cb build myself with against wx3.0.2 under Windows XP.
I see some similar issue, see screen shot:

sometimes, I see two cursors in the previous locations, see screen shot:

Here is the steps to reproduce:
When I first put the cursor after the "main()", and I hit the arrow down key. I see the cursor is still there. After that, I hit the arrow down key again, I see the cursor is still there after the "{", and now the cursor is located after the "vector".
I guess it is related to highlight of the "()" or "{}".

oBFusCATed:
It works fine on linux when using wx3.0, so it might be windows only issue.

@Morten: Are you able to reproduce the problem?

ollydbg:

--- Quote from: oBFusCATed on December 20, 2015, 02:30:52 pm ---It works fine on linux when using wx3.0, so it might be windows only issue.

--- End quote ---
It looks like it's an issue related to the "indicator" of the scintilla. I have download the latest wscite, but I don't know how to enable the brace indicator in it.

oBFusCATed:
Matching brace highlighting works fine on linux. No visual artefacts observed.

Navigation

[0] Message Index

[#] Next page