Author Topic: highlight of the select variable problem  (Read 10562 times)

Offline dje

  • Lives here!
  • ****
  • Posts: 683
Re: highlight of the select variable problem
« Reply #15 on: October 07, 2009, 10:42:48 am »
And if there is a way to export the profile to external file, one can be able to give his profile to a co-worker and everybody will edit files in the project the same, so the formating issues/commits will be less frequent.

+1 for this very nice and wanted  8) feature...
yes, but it is also possible to configure astyle properly and include an astyle step before commiting in the configuration management tool.

Dje

Offline ollydbg

  • Developer
  • Lives here!
  • *****
  • Posts: 5216
  • OpenCV and Robotics
    • Chinese OpenCV forum moderator
Re: highlight of the select variable problem
« Reply #16 on: March 02, 2011, 02:36:07 pm »
sorry for bump the old thread, I found a patch here:
http://developer.berlios.de/patch/?func=detailpatch&patch_id=3130&group_id=5358

the author said that "no cpu overload detected", it that true?
sometimes I still need to hightlight one char variable.
thanks.
If some piece of memory should be reused, turn them to variables (or const variables).
If some piece of operations should be reused, turn them to functions.
If they happened together, then turn them to classes.

Offline wf

  • Single posting newcomer
  • *
  • Posts: 2
Re: highlight of the select variable problem
« Reply #17 on: March 02, 2011, 06:31:26 pm »
I'm using this on windows + Process Explorer for monitoring cpu load. There is no cpu overload because if no text selected:
Code: [Select]
if (a == b)
     return
We return at the beginnig of function. Test it someone please.
^_^

Offline oBFusCATed

  • Developer
  • Lives here!
  • *****
  • Posts: 11653
    • Travis build status
Re: highlight of the select variable problem
« Reply #18 on: February 02, 2013, 02:39:15 am »
I've just committed patch #3130, which makes it possible to set the minimum of characters to 1.
The default is still 3, so the current behaviour should be unchanged.

About the slowness, yes there is slowness if the setting is set at 1 and I select 'e' in codecompletion.cpp for example.
It take 1-2 seconds to select all the occurrences. But generally it works OK.
(most of the time I ignore long posts)
[strangers don't send me private messages, I'll ignore them; post a topic in the forum, but first read the rules!]