what is the way for sprintf/prepend set with the line object
Hi.
I would like to use line object thanks to the numbre box to set the duration of the ramp.
With "sprintf" and prepend set there’s a problem because of the comma (need it for line.)
Is there an other way to do such thing ?
Thx.
ad
like this.
and next time, you should search the forum to see if your question has already been answered – i know for a fact i have answered this on a few occasions…
j
adrien schrieb:
> there’s a problem because of the comma (need it for line.)
You don’t need a comma for line, but to know that, you have to know what
the comma does, to find out that, there is plenty of documentation (and
archives) – there is no way to avoid the tutorials…
Stefan
–
Stefan Tiedje————x——-
–_____———–|————–
–(_|_ —-|—–|—–()——-
– _|_)—-|—–()————–
———-()——–www.ccmix.com
well well…
French was a joke…Sorry if you had not get it.
Don’t you know about urgency ??? I got to have this information very quickly, and during my research on cyling forums, I posted my problem, that’s all. You’re over reacting
If you don’t want to reply to my post just don’t answer my issue !
Anyway it has updated the point, is this so bad ???
Where is the open source spirit ??
Just if you don’t want reply, well don’t reply that’s all !!
It’s like Lycos chat, although I am not anger against anybody !
Just take it easy, and don’t waste time to reply my post if you don’t want to do it !
end of this "non-case".
ad
Quote: adrien wrote on Mon, 21 July 2008 17:49
—————————————————-
> Where is the open source spirit ??
—————————————————-
The Open Source spirit is here: < http://www.catb.org/~esr/faqs/smart-questions.html>, which is distributed on about 10,000 lists online.
And I quote…
Before asking a technical question by e-mail, or in a newsgroup, or on a website chat board, do the following:
1. Try to find an answer by searching the archives of the forum you plan to post to.
2. Try to find an answer by searching the Web.
3. Try to find an answer by reading the manual.
4. Try to find an answer by reading a FAQ.
5. Try to find an answer by inspection or experimentation.
6. Try to find an answer by asking a skilled friend.
7. If you’re a programmer, try to find an answer by reading the source code.
adrien,
we only pointed out what you havent done prior to posting… we’re not making a "non-case" or issue, we’re just stating the facts. all u have to do is accept that and move on.
you might have heard of an old english saying: "dont bite the hand that feeds you"
j