User forums > Using Code::Blocks

Bug in virtual folder managment

(1/2) > >>

Max:
I am starting to use the new virtual folder functionality. I am reporting a bug that is related to several
confusing behaviour of the project tree.

Basically you can create (or delete) a new folder but, then, you are not pushed to save the project.
Adding, or deleting,  a virtual folder the "save project" remains grey and you can close the project without save
the modification. Obviously you loose your changes.

Before opening a bug report I would like to get some confirmation (just to avoid useless bug reports)
Hope this helps

Max

Max:
oopss... latest nightly 2891 and Windows XP SP2

killerbot:
what you are saying is correct, I already informed the Don yesterday ;-)

mandrav:
Let's get something straight: virtual folders are properties of the files, not the project itself.
There is no point saving a virtual folder if it is empty. Obviously, if you create a virtual folder, the next thing you will normally do is drag all relevant files inside it. Once you do this, the project will be marked as dirty.

Max:
Uhm.. The project tree structure seems a project property (at least to me). Anyway I accept your point of view.

Now, after some tests, I got another strange behaviour.

A) I open one of my projects (see State1.png attached).
B) I create a new virtual folder called Test and i moved a file (adler32.h) in it See State2.png
C) Now the project is "dirty". I save it. I close it.
D) I reopen the project. Now I got what you can observe in State3.png.
Now there are two "Test" virtual folder.
Please note that I am using the "categorize by file type" AND " "Display folder as on disk"
E) If I delete the "test" virtual folder outside the "include" folder both (!) "test" virtsul folders disappear and the
project is not marked as dirty (the save project option id grey). I have to Save as the project to save changes.


Now another example. I deselect the "Display folder as on disk", so only "categorize by file type".
I started the same example from scratch.

After A I got State4.png
After B I got State5.png
After C and D I got State6.png

Now "Test" is empty and the file adler32.h is inside "include" with two \  before the name, i.e. \\Test\adler32.h


The overall behaviour seems not intuitive (at least to me) so I think there is a bug.

OK. Now I have the same problem with the attachment dimension. Using .png I got 140 K. So (mandrav please forgive me)
I am dividing the post in two. I am getting a internet area, so it should not happen again...


Hope this help

Max



[attachment deleted by admin]

Navigation

[0] Message Index

[#] Next page