Is it called because the form looses input focus?
==
There's no user interaction (where the form may loss input focus)
between OnEventLoopStarted and disabling widget in code. And why does
it only happens on disabling groupboxes ?
Check amodalresult for <> mr_canclose in treceditfo.clo
On Tuesday 12 November 2013 07:17:13 Ivanko B wrote:
> The unexpected code :
> ==
> procedure treceditfo.closequery(const sender: tcustommseform;
> var amodalresult: modalresultty);
> begin
> with viewform.getdataset do begin
> if (state <> dsBrowse) {and (changecount > 0)} then b
On Monday 11 November 2013 22:25:07 Sieghard wrote:
> My previous egregious example
>
> Register = RECORD
>Field_1: 0..77;
>Field_2: 1..3;
>Field_3: 5..25;
>Field_4: 111..112;
>Field_5: -2..-1;
> END;
>
On Monday 11 November 2013 21:38:18 Sieghard wrote:
> BTW, I like to use "copy & paste" for such repetitive stuff as declarations
> or such. When I have to create a table, I might even change editors when
> there's one around that can do column block manipulations, build the table,
> and possibly
On Monday 11 November 2013 20:27:10 Ivanko B wrote:
> 1) doubled "Copy to Clipboard" item in RLick popup menu of Stack window;
Please try again with git master 556709ca70c5b0a5090973e9d9c1201cf767780f.
> 2) requesting same dependent MFM files to load even if these files are
> already loaded as de
The unexpected code :
==
procedure treceditfo.closequery(const sender: tcustommseform;
var amodalresult: modalresultty);
begin
with viewform.getdataset do begin
if (state <> dsBrowse) {and (changecount > 0)} then begin
if (amodalresult = mr_cancel) then begin
cancelupdate; /
Hmm, it only happens with forms having tgroupbox widget(s) on them on
disabling these groupboxes. 100% reproducible in the PODPISKA.
--
November Webinars for C, C++, Fortran Developers
Accelerate application performance wi
Hallo Ivanko,
Du schriebst am Mon, 11 Nov 2013 11:37:24 +0500:
> Just have the compiler shift the (imaginary) base address
> =
> It may break connections with numbering in real-world task. What for
> to do it if keeping this connection doesn't slow down performance ?
Oh, you count the bi
Hallo Ivanko,
Du schriebst am Mon, 11 Nov 2013 14:34:40 +0500:
> For non-2^N ranging.
For this yone could consider to allow subrange types as basde types for bit
fields also - so you get "the better" of both things:
- you can specify the needed / wanted number of bits _and_
- you can specify t
Hallo Michael,
Du schriebst am Mon, 11 Nov 2013 10:00:17 +0100:
> On 11/08/2013 11:26 PM, Sieghard wrote:
> >
> > TYPE
> >MonthDay = 1..31;
> >WeekDay = 1..7;
> >CharBits = 5..9; { for serial interfaces }
> >
> > Not useful?
>
> IMHO Only really useful if you go on
>
> Type Workin
Hallo Michael,
Du schriebst am Mon, 11 Nov 2013 09:56:02 +0100:
> On 11/11/2013 05:35 AM, Ivanko B wrote:
> > You require theater seat numbers to start at 0 for each row as well?
> +1
>
> (If the count of seats is > 9 it would start with "00", of course.)
Okay - you get seat number 00. Go to th
Hallo Ivanko,
Du schriebst am Mon, 11 Nov 2013 09:41:58 +0500:
> The ALGOL syntax looks as a complication & seems to offer no benefits :)
The Algol syntax was the base for Pascal. It is very similar, although
Pascal left out many constructs possible even in the simpler Algol 60
dialect, like dyn
Hallo Ivanko,
Du schriebst am Mon, 11 Nov 2013 15:00:12 +0500:
> But "int" is already signed (as Sieghard pointed out) so "sint" is bad.
> ==
> That signedness isn't more than just a old (and not obvious) assumption.
It's a mathematical convention. The set of integer numbers usually
comp
Hallo Michael,
Du schriebst am Mon, 11 Nov 2013 11:42:58 +0100:
> On 11/11/2013 10:53 AM, Martin Schreiber wrote:
> >
> > Because if there is a "u" for unsigned there must be a "s" for signed
> > (orthogonality). But "int" is already signed (as Sieghard pointed out)
> > so "sint" is bad.
> While
Hallo Martin,
Du schriebst am Mon, 11 Nov 2013 07:07:00 +0100:
> > > Can you describe how "typing easy" with your editor program works so
> > > it is as easy to enter "cardinal32" as typing "card32"?
> >
> > Yes. It doesn't, as I don't _want_ to have such a feature. I _do_ want
...
> I think the
1) doubled "Copy to Clipboard" item in RLick popup menu of Stack window;
2) requesting same dependent MFM files to load even if these files are
already loaded as dependant of other form(s) loaded.
--
November Webinars for
On 11/11/2013 12:06 PM, Martin Schreiber wrote:
>
> Probably there is no need for an event handler. There is
> ttabwidget.tab_coloractivetab, ttabwidget.tab_fontactivetab or
> ttabpage.coloractivetab and ttabpage.fontactivetab.
>
ttabwidget.tab_coloractivetab does it.
Thanks.
Patrick
---
CloseQuery is somehow called :
-
procedure treceditfo.closequery(const sender: tcustommseform;
var amodalresult: modalresultty);
begin
with viewform.getdataset do begin
if (state <> dsBrowse) {and (changecount > 0)} then begin
if (amodalresult = mr_
Please set a breakpoint in the closequery method.
==
Tomorrow.
PS: When unexpected OnCloseQuey, "frame.caption" of tdbbooleandits
aren't grayed as long as the grpoupbox frame & checkbox areas of the
dbbooleanedits are grayed. "Grayed" means indicating the disabled
state.
--
On Monday 11 November 2013 17:20:00 Patrick Goupell wrote:
> Hello Martin,
>
> Is there a way / how can I change the background color of the ttabpage
> caption?
>
> I don't want to change the color of the whole page, just the caption
> that shows.
>
> What I am looking for is a way to quickly ident
Hello Martin,
Is there a way / how can I change the background color of the ttabpage
caption?
I don't want to change the color of the whole page, just the caption
that shows.
What I am looking for is a way to quickly identify what page is active
in a tabwidget if the pages have similar lookin
On Monday 11 November 2013 14:23:50 Ivanko B wrote:
> The call stack at firing is :
>
There is no closequery() in the stack? Please set a breakpoint in the
closequery method.
Martin
--
N
The call stack at firing is :
#0 006025DD receditform.pas:150
TRECEDITFO__WIDGETSDISABLE(ENABLED_TAG=1, this=)
#1 00602C4E receditform.pas:334
TRECEDITFO__STATECALLBACK(DEACT_STATE=true, this=)
#2 006028A1 receditform.pas:201
TRECEDITFO__EVENTLOOPSTARTED(SENDER=0
On 11/11/2013 12:15 PM, Martin Schreiber wrote:
> card32, int32 is based on Pascal types and unambiguous too. cardinal,
> integer -> recommended type, card, int -> size of the CPU registers.
Yep.
As said: mater of taste. So it's up to you.
-Michael
---
On Monday 11 November 2013 11:42:58 Michael Schnell wrote:
> On 11/11/2013 10:53 AM, Martin Schreiber wrote:
> > Because if there is a "u" for unsigned there must be a "s" for signed
> > (orthogonality). But "int" is already signed (as Sieghard pointed out)
> > so "sint" is bad.
>
> While I do see
That signedness isn't more than just a old (and not obvious) assumption.
But the "U" prefix may be considere as not a variation mark (assuming
such marks for other variations) but a value limitation. Then the
pairing "int + uint" makes sense.
--
On 11/11/2013 10:34 AM, Ivanko B wrote:
> Why not something like
>bitpacked RECORD
> Filed_1: integer: 7;
> Filed_2: integer: 2;
> Filed_3: integer: 5;
> Filed_4: integer: 1;
> Filed_5: integer: 1;
>end
> ===
> For non-2^N ranging.
>
On 11/11/2013 10:53 AM, Martin Schreiber wrote:
>
> Because if there is a "u" for unsigned there must be a "s" for signed
> (orthogonality). But "int" is already signed (as Sieghard pointed out)
> so "sint" is bad.
While I do see you point, IMHO this is trading strictness vs
readability, and thus
Use the watch window if you want to see processed
=
Very not handy :)
--
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming models. Explore
techniq
But "int" is already signed (as Sieghard pointed out) so "sint" is bad.
==
That signedness isn't more than just a old (and not obvious) assumption.
--
November Webinars for C, C++, Fortran Developers
Accelerate app
On Monday 11 November 2013 10:28:23 Ivanko B wrote:
> gdb provides the text.
> ==
> And MSEide processes it. Decoding would be very useful for recognizing
> widgets.
>
MSEide processes string variables. What you see in stack window is a record
parameter. The stack info and records
On Monday 11 November 2013 10:02:39 Michael Schnell wrote:
> On 11/08/2013 05:32 PM, Martin Schreiber wrote:
> > Or ord8, ord16, ord32, ord64, int8, int16, int32, int64?
>
> So why invent new names instead of using the really well known names
> such as "uint8_t", "int16_t"
>
Because if there i
Definitions like
-
var1: 0..22;
or
var1: integer from 0 to 22;
might by useful multiarch programming since compiler may select needed
internal (arch-specific) type - emulated 64bit even for 8-bit arch for
instance so that programs work in sam
This is not limited on a single hardware "Word", but can define
to arbitrary length memory areas.
==
Really, it's important for bitpacked data.
--
November Webinars for C, C++, Fortran Developers
Accelerate app
Why not something like
bitpacked RECORD
Filed_1: integer: 7;
Filed_2: integer: 2;
Filed_3: integer: 5;
Filed_4: integer: 1;
Filed_5: integer: 1;
end
===
For non-2^N ranging.
So why invent new names instead of using the really well known names
such as "uint8_t", "int16_t"
==
Sounds reasonable.
--
November Webinars for C, C++, Fortran Developers
Accelerate application performance
gdb provides the text.
==
And MSEide processes it. Decoding would be very useful for recognizing widgets.
--
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable
On 11/08/2013 07:46 PM, Martin Schreiber wrote:
>
> One probably would write
> "
>Register = bitpacked RECORD
> Field_1: $..$007f;
> Field_2: $..$0003;
> Field_3: $..$001f;
> Field_4: $..$0001;
> Fie
On 11/09/2013 08:27 PM, Sieghard wrote:
> C-ish type
IMHO C-ish stuff only should be avoided if there is not already a really
decent alternative in well known Pascal dialects.
In fact C-ish naming _should_ be used if the most well known (GNU) C
dialect or the most well known C-Libraries (glibc
On 11/08/2013 05:32 PM, Martin Schreiber wrote:
>
> Or ord8, ord16, ord32, ord64, int8, int16, int32, int64?
>
So why invent new names instead of using the really well known names
such as "uint8_t", "int16_t"
-Michael
-
On 11/08/2013 11:26 PM, Sieghard wrote:
>
> TYPE
>MonthDay = 1..31;
>WeekDay = 1..7;
>CharBits = 5..9; { for serial interfaces }
>
> Not useful?
IMHO Only really useful if you go on
Type WorkingHours = Array [MonthDay] of Integer;
or similar.
-Michael
---
On 11/11/2013 05:35 AM, Ivanko B wrote:
> You require theater seat numbers to start at 0 for each row as well?
+1
(If the count of seats is > 9 it would start with "00", of course.)
> Sine we'll have bit counts etc starting from 0 then it's more
> consistent to count everything numeric from 0 as w
On Monday 11 November 2013 08:56:12 Ivanko B wrote:
> See the attachment.
gdb provides the text.
Martin
--
November Webinars for C, C++, Fortran Developers
Accelerate application performance with scalable programming mod
On 11/10/2013 02:33 PM, Sieghard wrote:
> Don't try. There was _never_ a complete implementation of this
> language around for all the time being, although the foremost computer
> scientists of the time worked on these compilers (way back) then.
Martin does like a decent challenge :-) :-) .
-Mi
44 matches
Mail list logo
