Can not open file 'CB_20110528_rev7173_win32.7z' as archive
Hi
It seems there is a problem with the 7zip archive.Quote from: 7zip file managerCan not open file 'CB_20110528_rev7173_win32.7z' as archive
Regards
Xav'
Hi
It seems there is a problem with the 7zip archive.Quote from: 7zip file managerCan not open file 'CB_20110528_rev7173_win32.7z' as archive
Regards
Xav'
same
reuploaded, should be ok nowIt is...
Is this only my own experience?No, it is not, probably this bug is fixed in the debugger_branch. There the watches are vastly improved.
- pumped astyle plugin to "Artistic Style v2.02" (missing: allow access to new features via UI)
This causes an issue for the 'Gnu' coding style because it defaults to a spacing of 4 as of astyle 2.02.I don't know the coding style, but either it's a bug in astyle (in that case please blame the astyle team) or the style really has changed to be like that. What's the cause?
This causes an issue for the 'Gnu' coding style because it defaults to a spacing of 4 as of astyle 2.02.I don't know the coding style, but either it's a bug in astyle (in that case please blame the astyle team) or the style really has changed to be like that. What's the cause?
--indent=tab OR --indent=tab=# OR -t OR -t#
Indent using tab characters, assuming that each
tab is # spaces long. Not specifying # will result
in a default assumption of 4 spaces per tab.
In the meantime, if you could have the 'Indentation size (in spaces):' be available irregardless of coding style it would be greatly appreciated. ;)Are you sure that this would work? According to the astyle documentation the general named rules are not meant to be customised, meaning it is not defined how an additional option is handled...
In the meantime, if you could have the 'Indentation size (in spaces):' be available irregardless of coding style it would be greatly appreciated. ;)Are you sure that this would work? According to the astyle documentation the general named rules are not meant to be customised, meaning it is not defined how an additional option is handled...
Output filename : ..\..\..\..\Bin\Mingw\Catopsys_CB.dllThis is a mi-use of the option. The latter two options cannot contain a path, but a filename only. The path is compiled by the output file name. If you search the forums you'll find another post with exactly the same question and a more detailed explanation. Usually you should do this (searching) in the first place.
Import library filename : ..\..\..\..\Bin\Mingw\Catopsys_CB.dll.a
Definition filefilename : ..\..\..\..\Bin\Mingw\Catopsys_CB.dll.def
In the meantime, if you could have the 'Indentation size (in spaces):' be available irregardless of coding style it would be greatly appreciated. ;)Are you sure that this would work? According to the astyle documentation the general named rules are not meant to be customised, meaning it is not defined how an additional option is handled...
It works when I use astyle from command line.
FWIW, I also created an item in astyle's bug tracker: http://sourceforge.net/tracker/?func=detail&aid=3309674&group_id=2319&atid=102319
This is a design change with 2.02. All styles now default to 4. The
"styles" are now bracket styles instead of coding styles.