a one-time display bug in WeBuilder

[Hondoe]

Hi!

I've noticed the following bug in WeBulider:

First, I noticed it and then changed the internal browser from Auto-Detect to FireFox. that only made things worse so I changed it back to Auto-Detect.

Here are the steps (I am using the latest version of WeBuilder, FireFox, etc.):

1. I run WeBuilder

2. I open a web page

3. I click on Vertical Splilt

4. Nothing is displayed in the preview pane

but if I next open another file and click on Vertical Split, or close the file and re-open it, or toggle from horizontal to vertical split, the preview appears and functions fine for the rest of the session.

Also, if I close WeBuilder and follow the same steps again, the problem does not appear. In other words, it only happens the first time I run WeBuilder each bootup.

thanks

[mapleleaf]

That is a strange one but one wonders IF the configuration is correct.

I test my web pages with six different browsers(IE, FF(3.6 &4.0Ɵ10pre), Opera, Safari, Google Chrome and Maxthon) without any issues as you described.

Have you tried clearing your cache, cleaned out your temp/tmp files, etc?

When did you last do a de-fragmentation? IF you use WinXP, Vista or Win7 then you should regularly de-frag since NFTS is by its very nature very fragmentory.

These are just some of the things that come to mind.


mapleleaf
http://www.mirana.net

[Hondoe]

Dear Mapleleaf,

Yes it is certainly a strange behavior. The fact that it only happens once per computing session suggests that something is not getting initialized.

If it were a problem with my PC, don't you think it would recur every time I start the program?

I defrag regularly, and registry clean, and my PC is fast and working perfectly. I clean out my temp files regularly, too.

I'm using Windows 7 Professional 64 bit.

thanks

Hank

[davenz]

This happens to me so often I just regard it as one of the quirks of WeBuilder. It usually happens the first time I go to preview a page in any given session - the preview shows blank until I either click away and back to it or change from IE to Firefox preview. It doesn't seem to matter which preview or aspect (vertical or horizontal) is set and since it isn't a show-stopper, it doesn't bother me at all. I have never bothered reporting it as no one else (until now) even mentioned it. As I said, it is just one of the quirks I have become used to after using the software for a long time.

Dave
davethompson.co.nz

[Gatis]

Hi,

Thank you for reporting. However, I could not reproduce this problem. As you mentioned, nobody has reported it before, so we did not know it even exists.
Here is how I tested it:
1) closed all open files;
2) closed WeBuilder;
3) opened WeBuilder (no open files);
4) opened a "hello world" html file from local disk;
5) clicked on "Vertical split";
6) the preview showed up just fine.

Without further steps, we can't do anything about it currently.

Gatis

[davenz]

I can replicate as follows:

1. Open WeBuilder with or without a file open. If no file loaded, open one.

2. Ensure preview browser set to Firefox.

3. Click preview tab (vertical or horizontal, it doesn't matter which)

4. Look at blank preview (see attached image).



5. Click on whatever preview tab was not used in Step 3 and note preview now works.

6. This is 100% replicable using the above method.

Windows 7 Business, 6gb RAM, Intel i7 2.8gHz CPU, VelociRaptor 150gb Main Drive.

Dave
davethompson.co.nz

[Hondoe]

Wow! The http://download.blumentals.net/tools/Mo ... ol1905.exe provided by Karlis not only installed without any issues on my Win 7 64-bit system, but it solved my earlier mentioned annoyance:

That when I first ran WeBuilder, the preview would not appear the first time it was invoked.

After installing the MozillaControl1905, this problem vanished!

Great!

[Hondoe]

Unfortunately, the next time I booted up my computer, the problem still existed.

[davenz]

I also use that version of the control and this still happens every single time. However, because it only involves one extra mouse click, I do it automatically, so while it could be called a 'bug' at a real stretch, because it only happens on some machines and therefore only affects a handful of users - which unfortunately includes us, this is hardly criteria for assigning valuable development time. I'd rather see that effort going into some of the other improvements that will bring this editor right up there with the best of them.

Just my 2 cents, for what it's worth.

dave
davethompson.co.nz