autoclosing of html tags doesn't work!

[oscar]

hi,

i'm using webuilder 2010 v10.1.0.119 and a problem i'm having is that tag autoclosing simply doesn't work!

options -> preferences -> text editor -> auto complete -> "enable auto complete"
options -> preferences -> language options -> html -> "auto complete html tags"

both options are enabled and auto closing of tags still doesn't work and i'm out of ideas what the problem could be
searched all over the net, but no one seems to be have that problem but me

any help would be much appreciated.

[Gatis]

Hi,

Indeed, we have not received similar problem reports lately.

How long have you been experiencing this? Did it stat only lately? Has it ever before worked for you?

[oscar]

system
---------
os: windows 7 ultimate 32bit
mbo: asus p5ql pro
cpu: intel core 2 quad q6600
ram: 4 gb
gpu: radeon hd3850 256 mb


i've tried using this program about a year ago and then it didn't work so i just gave up and used another text editor

since i've been hearing all these great reports of the program lately, yesterday i installed webuilder trial again only to find and remiind myself why i gave up from it in the first place

so, the conclusion: it has never worked for me, it doesn't work now

tried multiple reinstalls, with the deletion of both /program files/blumentals AND appdata/blumentals AND running registry cleaners in between (ccleaner)

i also tried installing the software on a windows xp pro machine (virtual xp mode) and the problem is still there

in lack of better explanations, i thought it has something to do with spellchecking, but i tried all possible combinations of settings to no avail

interesting enough smart button shows up regularly for everything else but autoclosing of tags

example:
<div class=" then smart button pops up and autocompletes quotes for me, but never pops up if closing the opening tag of an element (example: <div>)


i just want to add that, apart from tihs problem, i think this software is the definition of a perfect text editor for web and i will be disappointed if i can't use it, because closing of tags plays a major role in coding speed

im more than willing to submit a video proof of the issue if it'll help in resolving the thing

[oscar]

i've uploaded a video that shows the exact problem i'm having with all the settings involved

you can find it at:
http://www.youtube.com/watch?v=nxRa-qEq8XA

please watch in 480p

[notuo]

Hi Oscar.

I don't use the editor as you but let me add my 5 cents. I am not sure even how you start with the tags...

Tow choices: (from my point of view)

1) Type <p> and the </p> appears immediately

2) I have the language browser docked. If I double click in any html element That appears complete in the document.

Maybe is not what you want, but at least is a way to accomplish it.

Hope this helps

[notuo]

Ok. I tried what you show and did this:

I typed < and wait. The small browser appeared.
I choose for example the a tag and I got <a
Then I typed space and get another windows I choose class and get class=""
I typed whatever between the quotes
Y went to the end of line and typed > and the </a> appeared.

My config is the same as yours regarding auto complete.

[oscar]

i understand what you're suggesting and tried that also before, but no matter in what way i type the opening tag, the closing one simply won't sow

regarding the "language browser" its just a too slow method for me
i'm used to type quickly a tag, get closing one, and then i go on adding attributes and such

i just can't get my head around what seems to be creating this problem

i've watched other code in the same software with no such bugs

occurs in htmlpad too

[notuo]

What you want is:

type < choose the proper tag
and get (for example)

<a|></a> with the cursor where the | bar is?

I am not sure but I think the answer will clarify others.

[oscar]

all i want is the following:

1. i type <div>
2. </div> shows up automatically after the above
3. resulting in <div></div>

regarding the cursor i really dont care where it is as long as i have the auto closing feature

[notuo]

Well, that works for me.

As soon I type the > I get the propper closing.

Don't kow what to say.

[oscar]

i've uploaded another video in which the software is installed from scratch and still auto close feature doesnt work

you can find it here:
http://www.youtube.com/watch?v=IxCaf_BlUB4

i also tried the method you suggested:

I typed < and wait. The small browser appeared.
I choose for example the a tag and I got <a
Then I typed space and get another windows I choose class and get class=""
I typed whatever between the quotes
Y went to the end of line and typed > and the </a> appeared.

that also doesnt work on my end

its unreal that no one else seems to be having this problem

thanks for all your help, i dont know what to say either
i would really like this software to be my next favorite editor, but the auto closing feature means everything to me

[notuo]

its unreal that no one else seems to be having this problem

Actually (from my experience) if some is working to "all" but me. I am the problem. You mentioned reinstalled the product; well, maybe is before that the issue that prevents something. I don't know for real. Let's hear the opinion of Karlis or Gatis.

[Gatis]

Hi,

It is very strange. We have not received complaints about this feature lately, really. Besides, the latest version of our editors is 10.2.0.121. However this should have no impact, because as far as I know, there have not been any changes regarding this lately, so it should work.
I could provide you with a special version where you would see debug messages for the auto-complete tag functionality, and we could understand what is going on.
If you are interested, please leave me a private message and give me your email address.

[Pro Covers FX]

I would un-install WeBuilder and re-install it, that's what I had to do to fix my problems
on Windows 7 Pro 64-bit.

Also check your download WeBuilder and right click it and then properties and make
sure the file is not BLOCKED! By Windows 7.

InsiteFX

[Gatis]

Hi,

In this case it seems there is a problem with System locale.
It turned out that some functions will not work, if a computer uses other than non-English input language (in this case it was Croatian).
If anybody else is having similar problem, try switching input language to English. It seems currently this is the only workaround we can suggest.
We will try to fix this problem.