I think, the ‘Widgets/Toolbars’ works not well. Sometimes, when I move over the icons, they show me with a blue color,
that they are selected, sometimes not.
[quote=“ThomasM”]I think, the ‘Widgets/Toolbars’ works not well. Sometimes, when I move over the icons, they show me with a blue color,
that they are selected, sometimes not.
Thomas[/quote]
Hmm, haven’t seen that myself - any tips for reproducing it?
[quote=“jules”][quote=“ThomasM”]I think, the ‘Widgets/Toolbars’ works not well. Sometimes, when I move over the icons, they show me with a blue color,
that they are selected, sometimes not.
Thomas[/quote]
Hmm, haven’t seen that myself - any tips for reproducing it?[/quote]
For example:
Move the mouse over the new document icon, move then out, then in…
so move inside and outside the same icon.
Oh, I found it! During the mouse movement I can see, that the selection area is to small or so.
I move the mouse from bottom to top, to the new doc icon and when the mouse is in the icon area,
it will change the color. But when I move on to the top, it change the color back (unselected).
Please, see images:
[attachment=2]Start.png[/attachment][attachment=1]Entry.png[/attachment][attachment=0]Move on.png[/attachment]
[quote=“jules”]Sigh… I fixed that problem MONTHS ago.
PLEASE check the latest version before reporting bugs. This kind of outdated post just wastes everybody’s time.[/quote]
:?:
I have compiled with the stable version v2.0.21 (from Sourceforge) and Visual Studio 2010 Express.
As I have seen (days before), that it’s possible to update to the new module version with the Introjucer very easy,
I tried it. I compiled the Jucer with the new version and it fails, the Demo too. So I have only the stable version v2.0.21
for the Demo.
Where can I get the current Demo version?
With the Introjucer updater I can get only the current modules.
Git? I have no git installed, sorry.
I repeat again and it was the first thing that I was annoyed when I started with Juce:
I can’t build the Jucer or the Demo only with the updated modules via the Introjucer Updater!
There are changes in the modules which affect the Jucer and the Demo (I have not tried yet to compile the Introjucer).
After that, I have installed the stable version again and build all extras, to have runable versions.
Go here to GitHub and click on the “Zip” button just above the “Files” tab. That will give you the most up to date JUCE version. Recompile the JuceDemo and Introjucer from the extras folder.
But really, just install mysysgit. Its dead small and quick and you will then be able to update your whole JUCE directory with a simple “git pull”.
We’re up to 2.0.25 now, but the latest introjucer should be able to download that version of the modules for you.
BTW, as I mentioned elsewhere I am shortly going to add some auto-update functionality for the introjucer, as there do seem to be a bizarre number of GIT-refuseniks out there! (But honestly, to be a programmer these days and not even have GIT installed seems a bit odd… Even if you don’t like it, it’s such a pervasive part of modern development that you can’t just ignore it)
[quote=“dave96”]Go here to GitHub and click on the “Zip” button just above the “Files” tab. That will give you the most up to date JUCE version. Recompile the JuceDemo and Introjucer from the extras folder.
But really, just install mysysgit. Its dead small and quick and you will then be able to update your whole JUCE directory with a simple “git pull”.[/quote]
Thanks!
Downloaded the ‘julianstorer-JUCE-2_0_release-401-g9961c99.zip’ opened the
Introjucer project in Visual Studio 2010 Express and the build fails, because:
'julianstorer-juce-9961c99\modules\juce_gui_extra\code_editor\juce_cpluspluscodetokeniserfunctions.h(548):
error C2864: ‘juce::CppTokeniserFunctions::StringIterator::numChars’ : only static const integral data members can be initialized within a class’
From the ‘juce_CPlusPlusCodeTokeniserFunctions.h’:
/** A class that the tokeniser can use to parse a string. */
struct StringIterator
{
StringIterator (const String& s) noexcept : t (s.getCharPointer()) {}
StringIterator (const String::CharPointerType& s) noexcept : t (s) {}
juce_wchar nextChar() noexcept { if (isEOF()) return 0; ++numChars; return t.getAndAdvance(); }
juce_wchar peekNextChar()noexcept { return *t; }
void skip() noexcept { if (! isEOF()) { ++t; ++numChars; } }
void skipWhitespace() noexcept { while (t.isWhitespace()) skip(); }
void skipToEndOfLine() noexcept { while (*t != '\r' && *t != '\n' && *t != 0) skip(); }
bool isEOF() const noexcept { return t.isEmpty(); }
String::CharPointerType t;
int numChars = 0;
};
I’ve still no idea what you’re talking about… You’re saying “why doesn’t it take the factory as an argument”, but those methods you quoted already do take the factory as an argument…(?)