to mseide-msegui-talk
under this subject ( General List .)
to the subject Filter-find like this the user can easily find them. How to
proceed with the moderator ?
Objet : Re: [MSEide-MSEgui-talk] General list for MSEide+MSEgui
On 9/21/18 12:52 PM, mohamed hamza wrote:
> Many tha
On 9/21/18 12:52 PM, mohamed hamza wrote:
>
> NB: the demo dbfiter2 has an exception error ?
>
Please try again with git master
6238275e6d12c864a32ecec68b95c8c3432a2143, there was an invalid db file.
Martin
___
mseide-msegui-talk mailing list
On 9/21/18 12:52 PM, mohamed hamza wrote:
> Many thanks for your advice.
> Is your algorithm valid regardless the number of fields in dataset ?
>
Yes.
> NB: the demo dbfiter2 has an exception error ?
>
Which one? Works for me.
Martin
___
Objet : Re: [MSEide-MSEgui-talk] General list for MSEide+MSEgui
On Wednesday 19 September 2018 19:42:02 mohamed hamza wrote:
> I think we have to go back to the last MSEIDE. I am still debugging
> mseuniverse/sample/db/dbfilter.prj. I do not know why the filter is reset
> each time we do
On Wednesday 19 September 2018 19:42:02 mohamed hamza wrote:
> I think we have to go back to the last MSEIDE. I am still debugging
> mseuniverse/sample/db/dbfilter.prj. I do not know why the filter is reset
> each time we do a filter and then a find ?
>
Because the fek_find also calls the filter
: mercredi 19 septembre 2018 14:19
À : mseide-msegui-talk@lists.sourceforge.net
Objet : Re: [MSEide-MSEgui-talk] General list for MSEide+MSEgui
On 9/19/18 6:13 AM, Martin Schreiber wrote:
> You expect that tdataset.onfilterrecord is called in a tlocalindex.find()
> call? It is not called cur
On 9/19/18 6:13 AM, Martin Schreiber wrote:
> You expect that tdataset.onfilterrecord is called in a tlocalindex.find()
> call? It is not called currently. Probably not easy to achieve without
> performance loss. I'll take a look.
>
Done, git master 5c75b84b5c543fff18e9fdef79f1b2c6cc50,
On Tuesday 18 September 2018 20:06:46 mohamed hamza wrote:
> Try to do a filter and then find a value outside the filter. ( using
> navigator)
>
> Ex
> values = ( 10,20,30,40)
> set filter to value > 20 values = ( 30,40) are listed
> try find 2020 is listed and the filter is off
>
I will not want to
order you
or ask you for an immediate response.
Best Regards.
Med.
De : Martin Schreiber
Envoyé : mardi 18 septembre 2018 16:06
À : mseide-msegui-talk@lists.sourceforge.net
Objet : Re: [MSEide-MSEgui-talk] General list for MSEide+MSEgui
On Tuesday
Try to do a filter and after that a find a value outside the fitler.
De : Martin Schreiber
Envoyé : mardi 18 septembre 2018 16:06
À : mseide-msegui-talk@lists.sourceforge.net
Objet : Re: [MSEide-MSEgui-talk] General list for MSEide+MSEgui
On Tuesday 18
On Tuesday 18 September 2018 11:47:18 mohamed hamza wrote:
> The problem is on findvariant and when the field to search is not a
> string.
>
> Here what I did.
>
> VarVar is a variant;
>
> procedure tmainfo.beforeendfilteredit(const sender: tmsebufdataset;
>const akind:
The problem is on findvariant and when the field to search is not a string.
Here what I did.
VarVar is a variant;
procedure tmainfo.beforeendfilteredit(const sender: tmsebufdataset;
const akind: filtereditkindty);
begin
i:=0;
with sender do begin
while
https://gitorious.org/mseuniverse/mseuniverse/source/attic/msedocumenting/mse/trunk/help/doc/msehelp.txt
=
Hmm,a titanic work (approx 3000 lines)! And some parts look like (poor
English) written by me.
--
On 09/10/2014 07:46 PM, Graeme Geldenhuys wrote:
* Start documenting the base units like mseactions, mseapplication,
mseevent etc. Then working your way up the class hierarchy. Use fpdoc's
ability to inherit documentation from parent classes so you don't have
to duplicate help contents.
On Friday 12 September 2014 19:30:41 Patrick Goupell wrote:
On 09/10/2014 07:46 PM, Graeme Geldenhuys wrote:
* Start documenting the base units like mseactions, mseapplication,
mseevent etc. Then working your way up the class hierarchy. Use fpdoc's
ability to inherit documentation from
On Wednesday 10 September 2014 15:25:38 Patrick Goupell wrote:
../mseide-msegui/lib/common/kernel/linux/msesocketintf.pas(0,0): Could
not find include file '..\msesocketintf.inc'
../mseide-msegui/lib/common/kernel/linux/msesysintf1.pas(0,0): Could not
find include file '..\msesysintf1.inc'
On 11/09/14 08:00, Martin Schreiber wrote:
It simplifies the compiler commandline.
OK, but complicates the code. ;-)
I thought MSEgui already has a very simplified compiler command line.
Three simple settings.
-Fu../lib/common/*
-Fu../lib/common/kernel/linux
-Fi../lib/common/kernel
On 11/09/14 09:39, Martin Schreiber wrote:
git master 3bb9f5b uses platform specific path delimiters.
Thanks!
G.
--
Want excitement?
Manually upgrade your production database.
When you want reliability, choose
On Thursday 11 September 2014 10:51:30 Graeme Geldenhuys wrote:
On 11/09/14 08:00, Martin Schreiber wrote:
It simplifies the compiler commandline.
OK, but complicates the code. ;-)
I thought MSEgui already has a very simplified compiler command line.
Three simple settings.
On 09/09/2014 07:40 PM, Graeme Geldenhuys wrote:
I fully agree [several times too ;-)]. Extensive and complete in
source documentation is a nightmare and obfuscates the code a lot.
G.
Graeme,
I am having some trouble with
mseide-msegui/lib/common/kernel/linux/*.pas units. fpdoc
On 10/09/14 14:25, Patrick Goupell wrote:
I am having some trouble with
mseide-msegui/lib/common/kernel/linux/*.pas units. fpdoc cannot find
some include files.
It's because Martin hard-coded the path to the include file (which isn't
needed), and because he used a Windows path delimiter,
On 09/09/2014 10:43 AM, Martin Schreiber wrote:
On Tuesday 09 September 2014 16:38:50 Patrick Goupell wrote:
Also, where isthe include file jconfig.inc which is used in the
frollowing units. fpdoc cannot find it.
in ../mseide-msegui/lib/common/fpccompatibility/
Thses are the only .inc
On 09/08/2014 01:03 PM, Ivanko B wrote:
Starting to work on the descriptions files
=
What will they contain ?
To start with the documentation generated from fpdoc will look like the
free pascal documentation:
http://www.freepascal.org/docs-html/rtl/objects/tobject.html
It's seems that now it's too late but it would be better to have
sources be self-documenting (for PasDoc processing like Ararat's
Synapse).
As the ideal worlflow, once Martin adds/changes smth then also puts
some formateed decription. It's a deal of half of a minute but saves
many hours nerves in
On 09/08/2014 01:55 PM, Ivanko B wrote:
It's seems that now it's too late but it would be better to have
sources be self-documenting (for PasDoc processing like Ararat's
Synapse).
As the ideal worlflow, once Martin adds/changes smth then also puts
some formateed decription. It's a deal of
And just who would place the comments in the code for the PasDoc program?
Would that be Martin?
==
Anyone allowed to edit the sources (via rollable back GIT commits for
sure). Or dedicated patches to send to Martin for applying by him.
Currently those may be others than Martin but
Also The PasDoc way won't make sources dirty since one will take only
beginning (declaration) part of files.
But PasDoc should be tested for correct propagating inherted methods
props and hiding private ones while generating DOC data - so that
each (own inherited) public/protected/published
On Monday 08 September 2014 19:55:11 Ivanko B wrote:
It's seems that now it's too late but it would be better to have
sources be self-documenting (for PasDoc processing like Ararat's
Synapse).
As the ideal worlflow, once Martin adds/changes smth then also puts
some formateed decription. It's
On 09/05/2014 09:35 AM, Patrick Goupell wrote:
On 09/05/2014 02:32 AM, Graeme Geldenhuys wrote:
Ah, now I see what you mean. When I started working with your XML
file I immediately commented all but the msedataedits unit and the
output was perfect, then added all the others back in, but
On Friday 05/09/2014 at 03:25, Patrick Goupell wrote:
Another thing you can try is to delete everything but the editwidgets
section from the mseide-msegui.xml file and run it. Now I see the
Constants, Types, Classes, Procedures and Functions and Index pages
generated.
Compare that output
On 09/03/2014 04:44 PM, Graeme Geldenhuys wrote:
On Wednesday 03/09/2014 at 14:54, Patrick Goupell wrote:
if I use a project file like this:
fpdoc --project=mseide-msegui.xml which has almost all o f the
mseide-msegui units in it
Can you please attach the project (xml) file, then I'll
On Thursday 04/09/2014 at 23:58, Graeme Geldenhuys wrote:
Out of interest, I generated HTML and INF help and here is some
information.
HTML:
- generated 37464 html pages
- Uncompressed size is 78.8 MB
INF:
- generated a single IPF file which I then
On 09/04/2014 06:58 PM, Graeme Geldenhuys wrote:
Thanks for that.
OK, the XML project file was missing some info. The options=...
information for each unit was empty. The value must be the FPC
compiler options (as if you were going to compile that unit). fpdoc
needs that to correctly
On 09/02/2014 06:11 PM, Graeme Geldenhuys wrote:
Hi Patrick,
I'm not 100% sure what you mean? fpdoc does generate a class details
which includes methods and properties. Documentation for types,
constants variables, enums etc are generated too. ALL code in Object
Pascal can be documented
On Wednesday 03/09/2014 at 14:54, Patrick Goupell wrote:
if I use a project file like this:
fpdoc --project=mseide-msegui.xml which has almost all o f the
mseide-msegui units in it
Can you please attach the project (xml) file, then I'll take a look.
Regards,
Graeme
Hi Patrick,
On Monday 01/09/2014 at 18:35, Patrick Goupell wrote:
Is there a way to get fpdoc to generate something that looks like the
mseide object inspector?
I would like to see the properties in the generated documentation
also.
I'm not 100% sure what you mean? fpdoc does generate a
On Monday 01/09/2014 at 14:04, Patrick Goupell wrote:
On 08/20/2014 05:40 PM, Graeme Geldenhuys wrote:
May I also suggest you use fpdoc's XML format for documentation. That
way you can use it to further generated HTML, PDF, CHM, INF, MAN
pages,
TXT etc help text.
The little bit of
On 08/20/2014 05:40 PM, Graeme Geldenhuys wrote:
May I also suggest you use fpdoc's XML format for documentation. That
way you can use it to further generated HTML, PDF, CHM, INF, MAN pages,
TXT etc help text.
The little bit of MSEgui documentation I have seen was just some random
On 08/20/2014 05:40 PM, Graeme Geldenhuys wrote:
May I also suggest you use fpdoc's XML format for documentation. That
way you can use it to further generated HTML, PDF, CHM, INF, MAN pages,
TXT etc help text.
The little bit of MSEgui documentation I have seen was just some random
On Monday 01 September 2014 19:35:14 Patrick Goupell wrote:
On 08/20/2014 05:40 PM, Graeme Geldenhuys wrote:
May I also suggest you use fpdoc's XML format for documentation. That
way you can use it to further generated HTML, PDF, CHM, INF, MAN pages,
TXT etc help text.
The little bit of
its ok , today the problem is gone .
still one question if you don't mind .
how can i bring the main form to the front of my environement ,
because i made a layout that dock every thing in single window . and
if i want to add/edit some controls i've to press F12 every time , so
it would be nice if
both methods dosen't work !!
you can see this flash movie
https://app.box.com/s/rht8kdet749mpkpg38m0
2014-08-24 9:53 UTC+01:00, Martin Schreiber mse00...@gmail.com:
On Sunday 24 August 2014 10:38:57 misu kun wrote:
its ok , today the problem is gone .
still one question if you don't mind .
Am 24.08.2014 um 11:47 schrieb misu kun:
both methods dosen't work !!
you can see this flash movie
https://app.box.com/s/rht8kdet749mpkpg38m0
2014-08-24 9:53 UTC+01:00, Martin Schreiber mse00...@gmail.com:
On Sunday 24 August 2014 10:38:57 misu kun wrote:
its ok , today the problem is
On Friday 22 August 2014 21:31:57 Michael wrote:
As within each (or at least many) IDE, in there are specialities
built-in, which are not normal to other IDEs. Or functionalities or
components, which are special within that programming environment only.
And for those items, a documentation
On Friday 22 August 2014 22:47:05 misu kun wrote:
learning by doing with mseide/msegui is a bit hard , you have to
tweaking tons of parametres in the object inspector , its too much
customizable , thats good ! (maybe) .
I would start with the default settings, they should be OK for normal use.
thanks it works now
so the treeview can't be constructed in design time ?
what dose (fieldedit) and (itemlist) property in treeeitemdit ?
--
Slashdot TV.
Video for Nerds. Stuff that matters.
http://tv.slashdot.org/
On Saturday 23 August 2014 11:28:49 misu kun wrote:
thanks it works now
so the treeview can't be constructed in design time ?
No.
what dose (fieldedit) and (itemlist) property in treeeitemdit ?
The fieldedit property can be used in oder to connect a trecordfieldedit
widget for editing the
On Saturday 23 August 2014 12:32:27 Martin Schreiber wrote:
The fieldedit property can be used in oder to connect a
trecordfieldedit widget for editing the listitem.valuetext property
instead of
using onupdaterowvalues. Possibly currently broken, I need to check.
Jup, there was a missing
thanks
how to disable auto scroll for the main window ?
also there is an issue (access violation) when you press enter twice
on object inspector's events fields , fill the name of the event and
then press enter twice on it
2014-08-23 12:17 UTC+01:00, Martin Schreiber mse00...@gmail.com:
On
On Saturday 23 August 2014 19:28:18 misu kun wrote:
thanks
how to disable auto scroll for the main window ?
What means disable auto scroll? Hiding the scrollbars?
Disable container.frame.sb*.options sbo_showauto.
also there is an issue (access violation) when you press enter twice
on
On 08/20/2014 05:40 PM, Graeme Geldenhuys wrote:
May I also suggest you use fpdoc's XML format for documentation. That
way you can use it to further generated HTML, PDF, CHM, INF, MAN pages,
TXT etc help text.
The little bit of MSEgui documentation I have seen was just some random
On 2014-08-22 13:45, Patrick Goupell wrote:
What kind of documentation would you most like to see?
With fpdoc you can cater for both. FPDoc allows example code and images
to be included with the documentation. For example, the URL's below
shows documentation of a unit that is part of the tiOPF
On Friday 22 August 2014 16:42:48 Graeme Geldenhuys wrote:
On 2014-08-22 13:45, Patrick Goupell wrote:
What kind of documentation would you most like to see?
With fpdoc you can cater for both. FPDoc allows example code and images
to be included with the documentation. For example, the URL's
On 2014-08-22 15:53, Martin Schreiber wrote:
IwankoB wrote scripts to produce MSEgui fpdoc skeletons:
That must have been a lot time ago with an old fpdoc version. With the
latest fpdoc you don't need to generate skeleton files any more - thus
no need to update skeleton files. A big relief to us
Gentlemen,
I think I´ve started a discussion on how to generate documentation,
which was not my intention.
Having searched brother google for MSEide + MSEgui samples, found only
2-3 on the MSEide + MSEgui internet page and a few on the git.
Same for description of features. It seems to me that
As within each (or at least many) IDE, in there are specialities
built-in, which are not normal to other IDEs. Or functionalities or
components, which are special within that programming environment only.
And for those items, a documentation and/or samples must exist, to bring
these features
learning by doing with mseide/msegui is a bit hard , you have to
tweaking tons of parametres in the object inspector , its too much
customizable , thats good ! (maybe) .
last night i tried construct a simple treeview , i spent maybe 30min
just to figure out how to do so , in the end i failed .
On 08/20/2014 09:04 PM, Michael wrote:
1. Issue a short description of (nearly) each component (widget),
describing its major functions and features.
2. Provide more simple programm samples, showing the functionality of
the software (e.g. MDI, embedded forms, skinning, database, etc.).
Please
Hey Martin,
having played with mseide-msegui a bit, but found it very difficult to
use. To use means, that there is almost no documentation nor sample
programms available, where you can pick up some information about usage
of components or features. To improve this excellent piece of software
On 08/20/2014 03:04 PM, Michael wrote:
Hey Martin,
having played with mseide-msegui a bit, but found it very difficult to
use. To use means, that there is almost no documentation nor sample
programms available, where you can pick up some information about usage
of components or features. To
On 2014-08-20 20:31, Patrick Goupell wrote:
know what components are actually used, we can document them. That way,
we could build up a larger set of samples / documentation for new users.
May I also suggest you use fpdoc's XML format for documentation. That
way you can use it to further
On Wednesday 20 August 2014 21:04:09 Michael wrote:
Hey Martin,
having played with mseide-msegui a bit, but found it very difficult to
use. To use means, that there is almost no documentation nor sample
programms available, where you can pick up some information about usage
of components or
62 matches
Mail list logo
