Re: [Guidolib-devel] Guido Questions

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

<html><head></head><body dir="auto" style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;"><div class="ApplePlainTextBody">Hi Michael, Difficult to answer on the graphic problem and the offset. I don’t know Direct2D. You should have a look at other device implementations. The fact is that normally there is no need for scaling (that’s transparent). As far as I can remember, it seems to me that there was a similar problem with the opengl device. Regarding the question #2 the answer is yes: the guido factory can create all sort of elements. It’s actually used by the parser to create the AR representation. The API is a bit ugly and could be greatly improved, especially by making it more functional. Currently it works entirely by side effect :-( And for the question #3: there is no hit testing mechanism but it should be easy to build one using the mapping api. Have a look at “GUIDOScoreMap.h” : there are methods to inspect the graphic score and to associate elements, rectangles and time intervals. If you need more information, it could be easy to extend. Best — Dominique <blockquote type="cite">Le 27 sept. 2019 à 17:44, Michael Chourdakis &lt;win...@gm...&gt; a écrit : I'm up to putting Quido to my sequencer. There are questions: 1. I'm trying to create a Direct2D device so Guido can use my normal render target, hardware accelerated. This is the output: &lt;image.png&gt; When using the implemented HDC, this is the correct one: &lt;image.png&gt; &lt;image.png&gt; It seems to me that some weird scaling occurs. This is my code: virtual void	DrawMusicSymbol(float x, float y, unsigned int inSymbolID) { EnsureBrush(); D2D1_RECT_F ly = { 0 }; wstring yy = inSymbolID; auto ty = MeasureString(mSys-&gt;WriteFactory, mCurrMusicFont.Text, yy.c_str(), yy.length()); // To measure width and height, irrelevant // The following is weird, probably ly.left = (NextOrigin.x + x)* Scale.x; ly.top = (NextOrigin.y + y)*Scale.y; ly.right = ly.left + std::get&lt;0&gt;(ty); ly.bottom = ly.top + std::get&lt;1&gt;(ty); mSys-&gt;rt-&gt;DrawTextW(yy.c_str(), yy.length(), mCurrMusicFont.Text, ly, NextColor); } I need to understand more on scaling perhaps. Any ideas? 2. Can the guido factory create all sort of elements? I want to create a score editor and I can use it if it can create everything, otherwise I will simply edit gmn sources with my code. 3. Is there a hit testing mechanism, information about where each element is drawn? Notes particularly. So they can be hit-tested with the mouse and edited perhaps. If not, I can make a keyboard-only editor. Best Regards, _______________________________________________ Guidolib-devel mailing list Gui...@li... https://lists.sourceforge.net/lists/listinfo/guidolib-devel </blockquote> </div></body></html>