I am still trying to track this. Can anyone explain what prevents a tool (like the graphic tool, where the style of the graphicTemplate is set to "rectangle") actually working as the user drags the mouse across a card? I have checked the cantSelect of the card and the cantModify of the stack, and they're both false, but i have a case where I just can't get the tool to allow a drag (it creates a graphic, but one can't resize it), nor can the pointer tool select the graphics on the card, even though they can be selected by script.
I just can't think what other factors are involved in stopping these tools working like they do in the IDE. I can't find anything in the LC Dictionary or the User Guide (in fact it would be hard to deduce from either of them that one can offer a user the kind of drawing tools which are present in the IDE, but that's another issue)> Any ideas, anyone? TIA Graham On 9 Jun 2013, at 12:51, Graham Samuel wrote: > Folks, I am struggling with an issue I reported before, but then I had other > scripting errors making it unclear what was going on. Having now cleared > these errors, I have the following situation: > > 1. I have a tools palette which permits the user to pick a graphics (vector > drawing) tool such as 'rectangle' > 2. When the tool is set, the user expects to create a graphic on one of two > visible cards in the program > 3. In the IDE this work perfectly. > 4. In the standalone (equally on Mac and PC), on one of the cards (the card > that matters to the user), the rectangle is drawn but it's always the same > size (a small square), and in fact corresponds to what happens in the IDE if > you pick a graphic tool and click without dragging. Logging tests reporting > the value of cantSelect for the card and reporting the firing of the > newGraphic handler show that it's all working apart from the drag: but the > really strange thing is that on the other visible card, the graphic creation > works perfectly. The difference I know about between the cards is that one > has only a single field on it, the other has a lot of graphics already. I am > not trying to draw on top of the graphics in these tests, although doing so > does in fact work in the IDE. > > The above shows definitively that I have done something to the 'problem' card > which does not show up in the IDE but does show up in the standalone. I think > this is by definition a bug, but before I attempt to report it, I would like > to pin it down somehow. > > Can anyone suggest a way of finding out what's going on? I am already looking > at tool selection, mouseDown, newGraphic - and I can't see anything wrong. I > don't know a way of checking that the ability of the tool to grab the handles > of a graphic has been inhibited, which is what seems to be happening. Maybe > there's a hidden property that does this? > > TIA > > Graham > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your subscription > preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
