Michael Haberler wrote:
> Am 03.05.2012 um 13:15 schrieb John Thornton:
>
>
>> Is there some reason that the MDI window can only have one line of code?
>> Every CNC control that I've touched (3 or so) allow you to enter as many
>> lines as you want in the MDI window.
>>
>
> There's no con
Jan,
Am 03.05.2012 um 22:37 schrieb Jan de Kruyf:
> 1. The matter of old Gene feeling ignored:
> This is at least in part caused by silly SourceForge that has ideas. I also
I'm sure the technicalities of a browser incompatibility can be worked out one
way or the other
> 2. The program vs MDI i
On 3 May 2012 22:32, EBo wrote:
> His response was "Do not
> fix it so that it is self consistently WRONG."
Indeed. In this case mah has fixed something which was definitely
wrong in the _development_ branch, and in the process has shown up a
quirk in unrelated code which has changed a behaviour
I will refrain from weighing in on this debate, but I thought I would
share a quotable quote -- when I was helping a postdoc understand some
code I found a bug, and fixed it on the fly. His response was "Do not
fix it so that it is self consistently WRONG."
EBo
On Thu, 3 May 2012 22:37:38
On Thu, 3 May 2012 22:52:48 +0200
Jan de Kruyf wrote:
> Sorry, Andy
> I meant to say just that but I am also a bit sleepy right now!
> Basically Michael needs to branch until such time he fixes the
> hangup. But HEAD is still with the bug as is, but with a warning.
> Or indeed people must not be
Sorry, Andy
I meant to say just that but I am also a bit sleepy right now!
Basically Michael needs to branch until such time he fixes the hangup. But
HEAD is still with the bug as is, but with a warning.
Or indeed people must not be so impatient and use 2.5 but that then also
needs the warning.
j.
On 3 May 2012 21:37, Jan de Kruyf wrote:
> 4. So I would vote to revert to a release before you disabled the faulty
> code, and publish a formal warning from the directors of the project on the
> users list.
I don't think this is the way to go. Nobody should be doing anything
that "matters" on t
Michael,
dont get too excited, we do understand you are busy, and this can of worms
causes issues, now that you have taken off the lid.
As it should, because any oldish project has issues like this. And they do
need to get resolved!! there is no doubt about that.
At the same time I personally *hig
Am 03.05.2012 um 17:35 schrieb Chris Radek:
> On Thu, May 03, 2012 at 01:35:13PM +0200, Michael Haberler wrote:
>>
>> note I proposed handling proper queuing of MDI commands by modifying
>> Axis to have a queue of MDI commands, and feed them to task one by one
>> within the interpreter state con
On Thu, May 03, 2012 at 01:35:13PM +0200, Michael Haberler wrote:
>
> note I proposed handling proper queuing of MDI commands by modifying
> Axis to have a queue of MDI commands, and feed them to task one by one
> within the interpreter state constraints.
I have said this before but maybe not pla
On 3 May 2012 12:15, John Thornton wrote:
> Is there some reason that the MDI window can only have one line of code?
Until the bugfix, there wasn't that limit. You could enter as many
lines as your bravery allowed.
--
atp
The idea that there is no such thing as objective truth is, quite simply,
Am 03.05.2012 um 13:15 schrieb John Thornton:
> Is there some reason that the MDI window can only have one line of code?
> Every CNC control that I've touched (3 or so) allow you to enter as many
> lines as you want in the MDI window.
There's no conceptual problem. The current interpreter has
Is there some reason that the MDI window can only have one line of code?
Every CNC control that I've touched (3 or so) allow you to enter as many
lines as you want in the MDI window.
John
On 5/2/2012 8:33 PM, Michael Haberler wrote:
> Gene reported that 'queuing MDI commands in master does not
Gene reported that 'queuing MDI commands in master does not work since MDI tab
is greyed out while last command running' (btw a bug report would still help if
to aggregate tracking)
this is due to
http://git.linuxcnc.org/gitweb?p=linuxcnc.git;a=commit;h=81f105b477699060d6c721a06034aceea31cb964
14 matches
Mail list logo
