Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

read only

<< < (2/3) > >>

daniloz:
@jens:

I am aware of that one and like it very much. However, the point is, if a file is already open and is read-only, then even after you go there and uncheck the Read-only attribute, you cannot edit the file. You have the close it and open again...

So, my first though was that the file status should be refresh after a change in the read-only checkbox... and all diverged to a more general discussion...

Thank you for taking me back to my initial point. Maybe this should be the first step in the implementation, a callback to whatever-is-needed-to-refresh-the-editor-read-only-attribute, so after the file properties dialog is closed, you can edit the file...

killerbot:
wrt read only, there another issue to. I think when you go to the properties of a file, and exclude if from compile/link, then the checkbox of readonly gets active, and one has to ,manually remove the readonly attribute.

Dunno, about the reloading, but if that does not happen automatically, I think it should .Closing and opening a file, that's so windows like ;-)

daniloz:

--- Quote from: killerbot on December 16, 2010, 07:13:19 pm ---wrt read only, there another issue to. I think when you go to the properties of a file, and exclude if from compile/link, then the checkbox of readonly gets active, and one has to ,manually remove the readonly attribute.

--- End quote ---
When I look into the auto-reloading for read-only, I'll have a look at it as well...



--- Quote from: killerbot on December 16, 2010, 07:13:19 pm ---Dunno, about the reloading, but if that does not happen automatically, I think it should .Closing and opening a file, that's so windows like ;-)

--- End quote ---
I am not 100% sure (and I don't have C::B available right now), but I think if you change the read-only attribute externally  (using TotalComander ;-), for example), then you can just switch to C::B ans start typing. BUT, if you use the file properties dialog inside C::B to untick the read-only, then you have to open and close the file in oder that the change is taken...

But anyway, I agree, that's so windows like :-p (btw, anyone - maybe jens - can report what's the behavior on *nix systems?)

@all:
I am still making my way through the source code, scintilla, wxwidgets and so on... so any hints about how the read-only attribute is treated (which class, updates etc..) would be MUCH appreciated... :-)

MortenMacFly:

--- Quote from: daniloz on December 16, 2010, 02:45:14 pm ---I am talking to Morten about it already, thank you...

--- End quote ---
an I am aware that I still have the task to create the patch. Hence time is limited atm... but it's not forgotten. Sorry.  :(

daniloz:

--- Quote from: MortenMacFly on December 18, 2010, 01:52:11 pm ---an I am aware that I still have the task to create the patch. Hence time is limited atm... but it's not forgotten. Sorry.  :(

--- End quote ---
No problemo... My time is still limited, so I can still say that I'm not working on this issue because I don't have the patch from you... :-)

Navigation

[0] Message Index

[#] Next page

[*] Previous page